Product discovery
research
Investigate a question or a competitive landscape from sources and record a dated, sourced note another session can decide from.
Say “research X”
Product discovery · Portable skill
Check whether the product still fits its goals and users and what the outcome evidence shows; read-only.
npx skills add gaboesquivel/flow-skills -s alignNatural language is the interface. Any of these, or your own words, reach the skill.
The product compared with its goals, problems, and metrics, and each outcome with the evidence ("did it land", "are we building the right thing"); shipped with impact unknown is a valid answer.
The authoritative, versioned instruction your agent follows, from skills/align/SKILL.md.
Are we building the right thing, and what does the evidence say? "Check alignment" compares what the product is with what it is meant to be, and each outcome with the evidence you can reach. This is the what and the why, never the how: code quality is review, shaping a new idea is explore, and updating documents is sync-docs.
A missing source is a finding, not a reason to stop or ask.
PRODUCT.md (problem, users, core journeys, first useful release, main and supporting metrics, kill criterion, riskiest assumptions, alternatives, non-goals), DESIGN.md for journey steps, accepted specs and decisions, and any roadmap or candidate stubs. A Proposed record or draft spec is planned, not intended fact. For "did it land", the shipped spec's Outcome line names the evidence to look at and the decision it informs.Map each core journey and stated problem to the capabilities that serve it, each implemented, partial, planned, or none. Then:
ship's liveness) from used and from the outcome moved, and leaves what no source shows unknown. "Shipped, impact unknown" is a valid answer; say what evidence would settle it and which decision waits on it.Unknown is never zero. Missing access never hides what can be established; never invent a value. For each gap, name the smallest response: reuse existing collection, then a manual or export count, before any new service.
Lead with a visual: the journey-to-capability map, and a metric table (metric, result, target, source, gap) when there is more than one. Then working, missing, drift, and complexity in a few lines each, citing evidence and separating fact from inference. End with up to three priorities ranked by impact on the stated vision and metrics. Omit empty sections; say when intent is too thin to judge.
Read-only: never edit, install tools, connect accounts, change tracking, or schedule work. Name the skill that would act (sync-docs, explore, to-spec, build) and wait.
Product discovery
Investigate a question or a competitive landscape from sources and record a dated, sourced note another session can decide from.
Say “research X”