Find the real problem behind a feature request before anyone scopes a solution — whose job is stuck, what evidence exists already, and what observation would prove the assumption wrong. Use when a request arrives phrased as a solution ("add a dashboard", "we need notifications"), when a team is about to build on a belief nobody has checked, or when asked whether something is worth building at all. Not for writing the spec once the problem is settled, not for ranking work that is already…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Product discovery
A feature request is an answer. Discovery is recovering the question it answers, and finding out
whether the question is real. Most of the evidence you need already exists and nobody has read it.
## When this fires
A request names a solution and not a problem; a plan rests on a belief about users that has never
been checked; someone asks whether a thing is worth building. It does not fire when the problem
and its evidence are already established and the job is to write the scope — that is
`prd-and-stories`.
## Procedure
1. **Split the request into solution and problem.** Write the request verbatim, then write the
sentence under it: who is trying to do what, and what happens today instead. If you cannot
write that second sentence from what you were given, that gap is the finding — say so before
going further.
2. **Name the person and the job.** A named role doing a specific task on a specific occasion
("a support agent closing a ticket after a refund"), not a segment. Ask who is *not* affected
too — a problem everyone allegedly has usually belongs to nobody in particular.
…
The line at the top of this page pins the label git:20260919.a0d4f55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_mt2zmjly3cx5livk
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/product-discovery
GET https://markdownregistry.com/api/v1/blob/167ba3bb9e5f3cfdc0269e68532dadb1dbd584930bfc44bc87016226736fd540
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Handle requested Agent Dispatcher work with direct execution or prepared specialist guidance. Includes named roles…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/model-routing/SKILL.md · Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
cbrock84/headcount · plugins/product/skills/product-discovery/SKILL.md · Finds out whether a problem is real and a solution would work, before building it — recruiting the right people…
majiayu000/spellbook · skills/product-discovery/SKILL.md · Product discovery and market research expert. Use when validating product ideas, conducting market research, user…
peterbamuhigire/chwezi-dev-engine · skills/product-business/product-discovery/SKILL.md · Use when testing whether a product, feature, or workflow deserves investment through risk framing, prototypes…
qa-aman/claude-skills · skills/by-role/pm/product-discovery/SKILL.md · Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to…
yannickyamo/skills · product-discovery/SKILL.md · Run continuous discovery to find problems worth solving. Use when setting up weekly discovery rhythm, building…
clickety-clacks/tightbeam · priv/kungfu/agentic-engineering/skills/product-discovery/SKILL.md · Drive an undefined or fuzzy product to a written spirit — elicit the real problem behind asks, reframe, deconflict, and…
martinolivero/saas-builder · skills/product-discovery/SKILL.md · This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to…