prd-generator
Skill0 starsChanged 3 days agoApache-2.0View on GitHub
Generate, critique, and refine PRDs, spec files, and roadmaps for initiative-level planning. Use to pressure-test and strengthen a PRD before planning. Triggers on "prd-generator", "prd generator".
32 other projects use a version of this.
Adopted by
Most recently taken up by
- goyalsandeep2k/claude-skillstheir own version, first seen Nov 16, 2026
- ahmadammarm/musyskillstheir own version, first seen Nov 8, 2026
- luongnv89/skillstheir own version, first seen Nov 6, 2026
- imohammadfaraz/claude-skills-for-product-managertheir own version, first seen Nov 1, 2026
- coco-research/cocotheir own version, first seen Nov 1, 2026
- hongphuc5497/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use user-story-generator, ui-ux-design and 7 more.
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.
nek1987Skilluser-story-generator
Generate user story generator operations. Auto-activating skill for Enterprise Workflows. Triggers on: user story generator, user story generator Part of the Enterprise Workflows skill category. Use when working with user story generator functionality. Trigger with phrases like "user story generator", "user generator", "user".
Also in 3 projects that use this
rogue-dev-studioSkillui-ux-design
Expert UI/UX design for product interfaces: user flows, information architecture, wireframes, interaction patterns, accessibility, and a mandatory theme/brand alignment gate against the active project (PROJECT.md, design docs, existing tokens/visual language). Use before or alongside frontend work when designing screens, reviewing mockups, or validating that proposed UI matches the project theme already in progress or about to ship.
Also in 3 projects that use this
dipaulavsSkillidea-validator
Validates app ideas before building. Analyzes market saturation, competitors, real demand vs stated interest, solo builder feasibility (2-4 weeks timeline), and monetization potential. Use when user asks to validate an idea, evaluate a concept, check if idea is worth building, or before starting a new project.
Also in 3 projects that use this
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
AnthropicSkillcompetitive-analysis
Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 5 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- coco-research/coco★ 797same name
- Fokkyp/claude-skills★ 211same name
- jamesrochabrun/skills★ 209same name
- hamzafarooq/claude-code-starter★ 145same name
- luongnv89/skills★ 145same name
- jaktestowac/awesome-copilot-for-testers★ 118same name
- ricneves-ai/flowgrammers-skills★ 115same name
- EmeaAppGbb/spec2cloud★ 100same name
- dhzrx/ai-pm-claude-skills★ 22same name
- Vann4799/ai-prd-generator★ 22same name
22 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- assay-begin-fastSkill
- assay-beginSkill
- assay-end-fastSkill
- assay-endSkill
- assay-nextSkill
- assay-reportSkill
- assay-worktreesSkill
- prd-interviewSkill
- tech-planSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Default to critical feedback over validation.
- Distinctive: line 40
Never critique based on partial reads.
- Very specific: line 82
Always include: explicit assumptions, open questions, a "Risks & Mitigations" section.
- Distinctive: line 87
Run Workflow 1 against your own output.
- Very specific: line 120
Default document format is markdown into docs/planning/{slug}/.
- Distinctive: line 121
Use tables for comparisons and severity indicators (🔴🟡🟢).
- Distinctive: line 126
Never prescribe a single framework.
- Distinctive: line 127
Never generate a PRD without flagging its own gaps.
- Distinctive: line 128
Never give generic advice.
- Distinctive: line 129
Never skip the hard question.
“Common” is measured: kept by at least 6 in 10 of the 27 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
PRD Generator
Philosophy
This skill is framework-neutral. When coaching, always present multiple applicable frameworks, explain tradeoffs between them, and let the user choose.
Default to critical feedback over validation. Always identify gaps, challenge assumptions, and ask hard questions — then offer constructive paths forward.
Context
This skill supports planning at initiative scope. In the assay-begin-fast pipeline it is
Phase 4: refine and self-critique the prd.md that prd-interview produced, then surface the
gaps before the review gate.
For collaborative PRD creation from a brief, use the prd-interview skill.
Capabilities
| Capability | Trigger Phrases | Output |
| Critique PRDs/Specs | "review my PRD", "critique this spec", "what's missing" | Structured critique with severity ratings |
| Generate PRDs | "write a PRD for", "create a spec", "draft requirements" | Complete PRD document (markdown) |
| Coach on Frameworks | "how should I prioritize", "explain RICE", "opportunity sizing" | Framework comparison with worked examples |
| Review Roadmaps | "review my roadmap", "prioritization feedback", "sequencing" | Prioritization analysis with alternative orderings |
Workflow 1: Critique PRDs/Specs
Step 1 — Read the full document
Never critique based on partial reads.
Step 2 — Score across dimensions
Rate each dimension as 🔴 Critical Gap, 🟡 Needs Work, or 🟢 Strong:
- Problem Definition — Is the problem clearly stated? Evidence it's real?
- User Understanding — Are target users defined and validated?
- Success Metrics — Measurable, time-bound, tied to outcomes?
- Scope Clarity — In/out of scope explicit? Hidden assumptions?
- Edge Cases & Risks — Failure modes, dependencies, technical risks?
- Stakeholder Alignment — Who approves, builds, is impacted?
- Feasibility Signal — Engineering reality considered?
- Verdict Honesty & Sandbox Discipline (Assay-specific) — Does the work keep the
sandboxed, observed run as the only thing that assigns
CLEAN/FLAGGED/MALICIOUS? Does the always-on floor stay intact? IsMALICIOUSreserved for a captured, reproduced behavior, never an inference from a skill's text? IsUNVERIFIEDhonestly used when the sandbox can't run the skill or the dangerous path never fires?
Step 3 — Identify the top 3 gaps
Step 4 — Ask the hard question
End every critique with ONE pointed question the author probably hasn't considered.
Workflow 2: Generate PRDs
Step 1 — Gather inputs
Step 2 — Select PRD depth
| Template | Best For | Depth |
| Lightweight Brief | Small features, experiments | 1-2 pages |
| Standard PRD | Mid-size features | 3-5 pages |
| Full Spec | Large initiatives | 5-10+ pages |
Problem Statement → Goals & Success Metrics → Users & Scenarios → Requirements → Technical Considerations (incl. sandbox/verdict impact) → Risks & Mitigations → Out of Scope.
Step 3 — Generate the PRD
Always include: explicit assumptions, open questions, a "Risks & Mitigations" section. Reference
the roadmap's R1..R9 and the capability (A1..A10) the work belongs to.
Step 4 — Self-critique
Run Workflow 1 against your own output. Flag 🔴/🟡 areas as "Areas to strengthen before sharing."
Workflow 3: Coach on Frameworks
Prioritization: RICE, ICE, MoSCoW, Kano, Weighted Scoring, Cost of Delay / WSJF. Problem discovery: Jobs-to-Be-Done, Opportunity Solution Trees, Double Diamond. Strategy: Porter's Five Forces, Blue Ocean, Wardley Mapping. Sizing: TAM/SAM/SOM, Fermi estimation.
Workflow 4: Review Roadmaps & Prioritization
| Approach | Optimizes For | Tradeoff |
| Impact-first | Maximum outcome per unit time | May defer foundational work |
| De-risk first | Reduce uncertainty early | Slower visible progress |
| Quick wins first | Momentum | May delay strategic bets |
| Dependencies-first | Unblock parallel work | Front-loads less exciting work |
Visual-First Preview
PRD: {slug}
├─ Problem ........... {one line}
├─ Goals/Metrics ..... {one line}
├─ Users/Scenarios ... {one line}
├─ Requirements ...... must:{n} should:{n} nice:{n}
├─ Technical ......... {sandbox/verdict impact in a phrase}
├─ Risks ............. {top risk}
└─ Out of scope ...... {one line}Output Format
- Default document format is markdown into
docs/planning/{slug}/. - Use tables for comparisons and severity indicators (🔴🟡🟢).
Anti-Patterns (Never Do These)
- Never just validate.
- Never prescribe a single framework.
- Never generate a PRD without flagging its own gaps.
- Never give generic advice.
- Never skip the hard question.
- Never wave through a static-only verdict dressed as verification — if a PRD's verdict
rests on a pattern match or a model's reading of the skill's text rather than an observed
sandbox run, or lets either assign
MALICIOUS/CLEAN, or rendersUNVERIFIEDasCLEAN, that's a 🔴 regardless of how good the rest is.
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.

