Stats
Actions
Tags
From discover
Defines PRD structure, user story format with 4 Risks assessment, EARS-format acceptance criteria, and delivery readiness thresholds. Use when writing PRDs, drafting user stories, defining acceptance criteria, or reviewing PRD quality and completeness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/discover:prd-standardsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Canonical reference for PRD quality — shared by both authoring and review workflows. Ensures the author and reviewer apply the same standards.
Canonical reference for PRD quality — shared by both authoring and review workflows. Ensures the author and reviewer apply the same standards.
| Task | Read |
|---|---|
| Writing or reviewing a full PRD | references/prd-template.md |
| Writing or reviewing acceptance criteria | references/acceptance-criteria.md |
| Assessing story readiness or drafting user stories | references/user-story-guide.md |
4 Risks framework, Confidence Meter (0-10), and OST hierarchy are foundational concepts. This skill operationalizes them in the PRD context — templates, thresholds, and format.
A discovery-driven PRD follows a standard structure with additive extensions. See references/prd-template.md for the authoritative template.
Core sections (standard PRD):
Discovery extensions (additive, never replace core sections):
Each user story follows the persona-grounded format with 4 Risks assessment. See references/user-story-guide.md for the full guide.
Key rules:
docs/product/personas/, not generic "user"All functional requirements use EARS-format acceptance criteria. See references/acceptance-criteria.md for patterns and examples.
Key rules:
npx claudepluginhub shinpr/claude-code-workflows --plugin discoverGenerates structured PRDs with problem, context, solution, user stories, acceptance criteria, metrics, risks, and out-of-scope items. Iteratively gathers info via questions, reviews docs/issues/templates.
Use this skill when the user asks to "write a PRD", "write a spec", "product requirements document", "generate a PRD", "turn this into a spec", "create product requirements", "write acceptance criteria", or explicitly asks for a PRD or product specification. This skill writes a full PRD. For a chained workflow with JTBD analysis, OST framing, and prototype-ready spec, use the /write-prd command instead. Do NOT use this skill if the user only wants to evaluate an idea strategically — use strategy-stack or the pre-mortem skill for that.
Create clear, unambiguous product requirements that prevent costly rework and enable execution. Use when scoping features, defining acceptance criteria, or ensuring alignment between product, design, and engineering.