prd

# PRD: Product Requirements Document Generate product specs at the right depth for the decision stage. From a quick one-pager to a full PRD to a technical RFC. ## When to Activate - User says "write a PRD", "product spec", "one-pager for X", "RFC for X" - User asks for requirements, a spec, or a brief for a feature - User says "spec this out" or "document the requirements" ## Depth Modes Auto-detect from user phrasing. If ambiguous, ask. | Mode | When | Length | Contains | |------|------|--------|----------| | **One-pager** | Early exploration, exec alignment | 1 page | Problem, hypothesis, success criteria, key risks | | **Brief** | Ready to start design/discovery | 2-3 pages | Above + user stories, scope (in/out), dependencies | | **Full PRD** | Ready to build | 4-8 pages | Above + detailed requirements, edge cases, metrics, rollout plan, open questions | | **RFC** | Technical decision needed | 2-5 pages | Context, proposal, alternatives considered, tradeoffs, migration plan | ### Detection heuristics - "quick spec", "one-pager", "executive summary" → One-pager - "brief", "enough to start building", "design brief" → Brief - "PRD", "full spec", "detailed requirements" → Full PRD - "RFC", "tech spec", "architecture decision", "should we migrate" → RFC ## Process ### Step 1: Gather Context Before writing, check for existing context: 1. **Check for market-research output**: If competitive analysis exists for this domain, reference it 2. **Check memory**: Look for pro...