prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. After PRD is confirmed, use /prd-to-spec (optional) for technical design, then /to-issues to create implementable tickets. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out, 写PRD, 需求文档, 需求分析, 规格说明.
npx skills add smallnest/goal-workflow --skill prd --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PRD Generator Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation. After PRD is confirmed, use `/to-issues` to decompose it into Issues, and optionally `/prd-to-spec` for technical design before that. --- ## The Job 1. Receive a feature description from the user 2. Ask clarifying questions to cover key ambiguities — scale the count to complexity, not a fixed number (see Step 1) 3. Generate a structured PRD based on answers 4. **Present PRD to user for review** — ask "Please review the PRD. Let me know if any adjustments are needed, or reply OK to confirm." 5. Apply any adjustments, then save to `tasks/prd-[feature-name].md` 6. **Suggest next steps** (see Step 3) **Important:** Do NOT start implementing. Just create the PRD. --- ## Step 1: Clarifying Questions Ask only critical questions where the initial prompt is ambiguous. **Scale the number of questions to the feature's complexity — the goal is covering key ambiguities, not hitting a fixed count:** - **Simple, well-scoped feature:** 2-3 questions - **Typical feature:** 3-5 questions - **Complex feature** (multiple user roles, cross-system integration, significant ambiguity
- The Job
- Step 1: Clarifying Questions
- Format Questions Like This:
- Edge Cases & Fallback
- Step 2: PRD Structure
- 1. Introduction/Overview
- 2. Goals
- 3. User Stories
- 4. Functional Requirements
- 5. Non-Goals (Out of Scope)
- 6. Design Considerations (Optional)
- 7. Technical Considerations (Optional)
- 8. Success Metrics
- 9. Open Questions
What does the prd skill do?
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. After PRD is confirmed, use /prd-to-spec (optional) for technical design, then /to-issues to create implementable tickets. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out, 写PRD, 需求文档, 需求分析, 规格说明.
How do I install it?
Run `npx skills add smallnest/goal-workflow --skill prd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From smallnest/goal-workflow, a repository with 199 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.