Finds out whether a problem is real and a solution would work, before building it — recruiting the right people, interviewing without leading them, separating what users say from what they do, naming the riskiest assumption and testing that one first, and reaching a decision rather than a summary. Use this to validate a problem, test an idea cheaply, decide whether to build something, or fix a discovery process that keeps confirming what the team already believed.
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
Discovery is how you find out you were wrong while it is still cheap. A process that never kills
anything is not discovery, it is a preparation ritual with research attached.
## Start from the assumption that would sink this if it were false
Every idea rests on a stack: that the problem exists, that people care enough to change what they
do, that your approach solves it, that they would pay, that you can build and deliver it. They are
not equally uncertain, and testing them in order of comfort is how teams spend six weeks confirming
the safe one.
Write the assumptions down, mark the one that would be most damaging to be wrong about, and test
that one first. Usually it is the second: the problem is real, and people are living with it
comfortably enough not to move.
## Recruit the people who have the problem, not the people who are easy to reach
Interviewing your friendliest customers produces reliable encouragement. Talk to people who churned,
people who evaluated and chose something else, and people who solved it another way — those three
groups carry most of the information.
…
The line at the top of this page pins the label git:20260901.9844f9d, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4097 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gg6a5zaazjeex5tn
GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/product-discovery
GET https://markdownregistry.com/api/v1/blob/751d96d2a65ff8532a977f545b9263c0a98d6519c3246f2cbdf61e0a73203d0e
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.
cbrock84/headcount · plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md · Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development…
cbrock84/headcount · plugins/corporate-strategy/skills/market-entry/SKILL.md · Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report…
cbrock84/headcount · plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md · Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or…
cbrock84/headcount · plugins/corporate-strategy/skills/scenario-planning/SKILL.md · Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting…
cbrock84/headcount · plugins/corporate-strategy/skills/strategic-alliances/SKILL.md · Structures partnerships that change what the business can do — technology integrations, channel and reseller…
cbrock84/headcount · plugins/customer-experience/skills/chief-customer-officer/SKILL.md · Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product…
cbrock84/headcount · plugins/customer-experience/skills/customer-onboarding-and-implementation/SKILL.md · Takes a new customer from signature to working — setting a definition of live that both sides agreed before the…
cbrock84/headcount · plugins/customer-experience/skills/customer-success-management/SKILL.md · Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a…
cbrock84/headcount · plugins/customer-experience/skills/escalation-management/SKILL.md · Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive…
cbrock84/headcount · plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md · Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting…
majiayu000/spellbook · skills/product-discovery/SKILL.md · Product discovery and market research expert. Use when validating product ideas, conducting market research, user…
nahid-sparktales/agent-dispatcher · skills/product/product-discovery/SKILL.md · Find the real problem behind a feature request before anyone scopes a solution — whose job is stuck, what evidence…
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…
