| name | prd |
| description | Create or refine product requirements documents for feature ideas, MVPs, and roadmap items. Use when the user asks for PRDs, requirements, scope definition, user stories, success metrics, non-goals, or implementation-ready feature specs. |
PRD
Overview
Create developer-readable PRDs with clear scope, explicit assumptions, and measurable outcomes.
Workflow
- Analyze the request and infer all available context before asking questions.
- Ask 3-5 clarifying questions only for information that materially changes scope or requirements.
- Draft the PRD using the standard structure in
references/prd-structure.md.
- Mark unknown details as assumptions; avoid blocking on non-critical ambiguity.
- Save the document with date-prefixed naming.
- Ask whether the user wants revisions or task breakdown next.
Output Rules
- Use filename format:
YYYY-MM-DD_<feature-name>_prd.md.
- Save to
personal/projects/<name>/drafts/ if project context is active.
- Otherwise save to
personal/drafts/.
- Do not start implementation unless explicitly requested.
References
- Read
references/prd-structure.md for required sections, question format, and quality checks.
