product-discovery
Skill0 starsChanged 2 months agoMITView on GitHub
Convert product ideas into clear problems, users, goals, and success metrics.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- snowfluke/tech-lead-skillstheir own version, first seen Nov 8, 2026
- ceeinbeta/pm-skillstheir own version, first seen Nov 1, 2026
- mcveloria/pm-skillstheir own version, first seen Oct 25, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- protocol/peruntheir own version, first seen Oct 17, 2026
Used with
Projects with it also use product-strategy.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
yannickYamoSkillproduct-strategy
Build product strategy that drives real choices. Use when defining where to play and how to win, creating strategy canvases, defining ICP/Anti-ICP, positioning products, setting pricing strategy, planning GTM motions, or structuring strategic bets. Part of the Modern Product Operating Model collection.
Also in 4 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- magnus919/agent-skills★ 172same name
- nahid-sparktales/agent-dispatcher★ 59same name
- ncklrs/startup-os-skills★ 51same name
- yannickYamo/skills★ 23same name
- Hassaan146/claude-skills★ 18same name
- ipavelm/ultimate-product-discovery-skill★ 15same name
- snowfluke/my-tech-lead-flow★ 8same name
- snowfluke/tech-lead-skills★ 8same name
- dkpapadopoulos/auto-claude-skills★ 6same name
- MartinOlivero/saas-builder★ 4same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- project-analysisSkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use when the task matches: product-discovery, idea, problem framing.
- Distinctive: line 27
Do not design screens or write code in this skill.
- Distinctive: line 40
Keep Product validation and engineering verification distinct.
- Distinctive: line 41
Do not claim completion without evidence.
- Distinctive: line 45
Do not invent business rules to fill gaps.
- Distinctive: line 46
Do not jump to React/FSD implementation.
- Distinctive: line 47
Do not load delivery skills during discovery.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
product-discovery
When to use
Use when the task matches: product-discovery, idea, problem framing.
Purpose
Turn vague requests into a shared problem statement Product roles can verify.
Inputs
- Plain-language idea or request
- Known users and constraints
Process
- Restate the request as a customer/user problem.
- Identify who is affected and in which context.
- Capture the business goal and observable success measures.
- List unknowns; stop for Product answers when material.
- Do not design screens or write code in this skill.
Outputs
- Problem statement
- Users in scope
- Business goal
- Success metrics
- Open questions
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not invent business rules to fill gaps.
- Do not jump to React/FSD implementation.
- Do not load delivery skills during discovery.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.