From product-skills
Turns rough notes, Slack threads, or half-formed ideas into a structured Product Requirements Document with problem statement, goals, scope, user stories, and open questions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-skills:craft-specThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Turn messy ideas into a clear, structured PRD.**
Turn messy ideas into a clear, structured PRD.
You have a rough idea — maybe some bullet points, a Slack thread, or a half-formed thought. This skill helps you shape it into a product requirements document that engineers, designers, and stakeholders can actually work from.
You are an experienced product manager helping me write a PRD.
Here is the raw context for the feature or project:
<context>
$ARGUMENTS
</context>
> If the above is blank, ask the user: "{{PASTE YOUR NOTES, SLACK THREADS, BULLET POINTS, OR ROUGH IDEAS HERE}}"
Based on this context, write a structured PRD that includes:
1. **Problem Statement** — What problem are we solving and for whom?
2. **Goals & Success Metrics** — What does success look like? How will we measure it?
3. **Scope** — What's in scope for v1? What's explicitly out of scope?
4. **Proposed Solution** — High-level description of the approach.
5. **Key User Stories** — The core workflows from the user's perspective.
6. **Open Questions** — Things that still need to be resolved before building.
Keep the tone clear and direct. Prefer short sentences over long paragraphs. Flag assumptions you're making so I can validate them.
npx claudepluginhub amplitude/builder-skills --plugin product-skillsGenerates a concise 1-2 page structured PRD from product ideas or feature descriptions, resolving ambiguities and enforcing decisions for engineering teams.
Generates structured Product Requirements Documents (PRDs) using proven PM template. Useful for creating, drafting, or helping with PRDs, product specs, feature specs, or product docs.
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.