agentsclimarketplace

Revisit

Skill codeeater/where-to-plai-plugin/plugins/where-to-plai/skills/revisit

This skill should be used to re-open and update an existing Market Opportunity Navigator as new evidence arrives — the longitudinal "breathing" loop. Triggers include "revisit our where to play", "we learned something new", "update the navigator", "re-evaluate our opportunities", "new customer interviews", "should we change our primary market", "our assumptions changed", "breathe the worksheets". Use it to scan the workspace for new inputs, flag assumptions and scores to revisit, and prompt re-scoring without silently overwriting prior judgement.From its SKILL.md

Install
npx -y skills add codeeater/where-to-plai-plugin --skill revisit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.6 KB, 657 tokens by cl100k_base, as published. Nobody here has run it

Revisit — the breathing loop

The Market Opportunity Navigator is a living, "breathing" companion you refine, revise, and adapt, not a one-time snapshot. Empirically most startups change their initial market-entry decision within the first few years. This skill re-opens the worksheets when new information puts the current strategy in doubt — and keeps the human's prior judgement visible, never silently overwritten.

When to run

Run when any of these occur: new customer interviews or market data; a tested assumption is confirmed or refuted; running low on runway ("oxygen"); a branding/identity decision looms; or simply on a periodic review cadence. See references/revisit-guide.md for the full list of re-evaluation triggers.

What to do

  1. Scan for new inputs. Look across the user's project — the where-to-play/ workspace and any new notes, interview transcripts, research files, or data the team dropped in. List what is new since the worksheets were last touched.

  2. Map new evidence to assumptions. Open where-to-play/assumptions.md. For each new input, identify which assumptions it confirms, refutes, or adds. Update the Evidence × Importance position. Move confidence colours accordingly (🔴→🟠→🟢, or back).

  3. Flag what to revisit — don't overwrite. Identify the factor scores (Worksheet 2) and focus choices (Worksheet 3) that this evidence calls into question. Present them as a change-list with the old value, the new evidence, and the implication. Record the prior score and reasoning alongside the proposed change (append, keep history) so the team can see what changed and why.

  4. Hand the decisions back to the team. Re-scoring and any change of Primary/Backup/Growth are the team's calls. Route to the attractiveness-map skill to re-score flagged factors, and to the agile-focus skill if the focus strategy itself is in question. Never auto-change a score or a primary.

  5. Record the breath. Date the update and note what triggered this revisit at the top of the affected worksheet(s), and save it so you can always go back for a review — the navigator should show its history of learning. Update the Breathing log line on each worksheet you touched: set Last reviewed to today and Next review per the agreed cadence.

Boundaries

  • Surface and propose; the team decides. Preserve prior human judgement as history, not as something to quietly replace. Let the navigator be a mirror, not a flatterer: test new evidence against the current strategy — don't let it rationalize a decision already made.
  • A confirmed-or-refuted assumption is progress either way — "not attractive anymore" is a valid, valuable update, and learning it now, before more sweat, tears and money, is a win rather than a setback.

Additional resources

  • references/revisit-guide.md — the re-evaluation triggers, the assumption-map mechanics, and how to keep score history without overwriting.

What ships with it: 1 file

2.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.