product-discovery
Skill8 starsChanged 44 days agoNo licenceView on GitHub
Optional pre-pipeline skill for when there are no user stories or acceptance criteria yet. Interviews the user about a raw product idea, then synthesizes the result into the Markdown table of user stories, acceptance criteria, and a sprint breakdown that the rest of the tech-lead pipeline (grooming, us-ac-formatter) consumes as its step-1 input. Use when the user has an idea but no written requirements, wants to start a project from scratch, says "I don't have user stories yet", "help me figure out the requirements", "turn this idea into stories", or asks where to begin.
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-skillsword for word, 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 · 1
- snowfluke/tech-lead-skills★ 8100% same
Edited · 0
None found.
Wrote their own version · 22
- 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
- dkpapadopoulos/auto-claude-skills★ 6same name
- MartinOlivero/saas-builder★ 4same name
- Uwayxt/agent-skills★ 4same name
- ceeinbeta/pm-skills★ 3same name
12 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 repository19 other files it gives its agents.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- lead-reviewSkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- tech-lead-setupsSkill
- technical-specSkill
- test-auditSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- troubleshootingSkill
- us-ac-formatterSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 20 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.
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.