product-requirements
Skill9 starsChanged 4 months agoNo licenceView on GitHub
Turns a chosen customer segment and its Core Jobs into a build-ready product requirements document — full functionality plus roughly 90% of the edge cases. It consumes upstream work (segments from /market-research, value direction from /value-prop) and never re-derives them; when there is no prior research it either routes you upstream first or accepts a segment and value you describe by hand for a fast pass. Before any requirement is written it runs a "challenge the build" gate — looking for a cheaper or more effective way to hit the same business goal, and if one wins, the PRD is written for that instead. The deliverable is a single document mapping each piece of functionality from Core Job to Aspiration Job to the value mechanic it uses to its success criteria to its Aha Moment, laid out along the Delivery Chain, with an edge-case table covering about 90% of real-world variation. Two modes: Quick (default, offline, one pass) and Deep (subagents plus a web parity check). Plain language, defaults to English. Reach for it when someone says "write the PRD" or "turn this segment and value into a build spec."
11 other projects use a version of this.
Adopted by
Most recently taken up by
- ratatatatcode/skillstheir own version, first seen Nov 15, 2026
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- astDeniss/business-skillstheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- ch4570/vulporatheir own version, first seen Oct 11, 2026
- cexll/myclaudetheir own version, first seen Oct 8, 2026
Used with
Projects with it also use test-cases and browser.
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.
cexllSkilltest-cases
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
Also in 3 projects that use this
zjing123Skillbrowser
Minimal Chrome DevTools Protocol tools for browser automation and scraping. Use when you need to start Chrome, navigate pages, execute JavaScript, take screenshots, or interactively pick DOM elements. Triggers include "browse website", "scrape page", "take screenshot", "automate browser", "extract DOM", "web scraping".
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- cexll/myclaude★ 2.8ksame name
- ssdeanx/AgentStack★ 44same name
- CrowPus/Zelyq★ 10same name
- astDeniss/business-skills★ 8same name
- swap-cameroon/kuro-antigravity-config★ 2same name
- ch4570/vulpora★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
- yiweiwan/skills★ 1same name
- limboinf/myskills★ 0same name
- ratatatatcode/skills★ 0same name
1 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 repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- improveSkill
- advisorSkill
- analyze-interviewsSkill
- anti-best-practiceSkill
- brainstormingSkill
- caveman-distillateSkill
- ce-ideateSkill
- claude-md-improverSkill
- code-modernizationSkill
- command-creatorSkill
- decision-matrixSkill
- diagnoseSkill
- docxSkill
- go-to-marketSkill
- grill-meSkill
- humanizerSkill
- improve-codebase-architectureSkill
- karpathy-guidelinesSkill
- market-researchSkill
- orchestrateSkill
- pdf-creatorSkill
- planningSkill
- report-writerSkill
- security-scanSkill
- session-reportSkill
- spec-normalizerSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- ui-first-principlesSkill
- ui-ux-pro-maxSkill
- value-propSkill
- verification-passSkill
- webapp-testingSkill
- workflow-plannerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
4
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 10 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.

