prd-enginelisted

# PRD Engine Generate agent-executable Product Requirements Documents using parallel research agents, structured synthesis, and quality scoring. Produces PRDs with before/after code blocks, verification tables, acceptance criteria, and explicit scope boundaries. For quick internal feature specs without research, use the `product-manager` agent directly instead. --- ## 1. Quick Start **Step 1: Describe the feature.** ``` You: "Write a PRD for adding dark mode to the dashboard" You: "PRD for the payment integration API --deep" You: "Quick PRD for fixing the header alignment bug" ``` **Step 2: Review the plan.** The engine shows agents, intensity, and estimated time before spawning anything. **Step 3: Say "go".** Or adjust: `more agents`, `fewer agents`, `add clarification`, `cancel`. **Step 4: Wait.** Research agents run in parallel (background). Synthesis and quality gate run sequentially. Progress updates appear as agents complete. **Step 5: Review.** Final PRD is delivered to `.prd-engine/{slug}/PRD.md` with a summary of quality score, requirement count, files touched, and next steps. --- ## 2. How It Works The engine runs a 3-phase pipeline with 4-19 agents depending on intensity: ``` Phase 1: RESEARCH (parallel, background) 3-8 Opus agents investigate the feature from orthogonal perspectives: codebase analysis, domain research, requirements, risks/edge cases, implementation strategy. Higher tiers double key agents for depth. Each writes a numbered repo