prd-to-spec

# prd-to-spec — PRD to Technical Specification Transform a Product Requirements Document (PRD) into a detailed technical SPEC that an engineer or AI agent can implement against. The PRD says *what* to build; the SPEC says *how* to build it. --- ## When to Use - A `/prd` has been generated and you need to bridge the gap to implementation - You want architecture decisions documented before coding starts - Multiple developers/agents will implement the feature and need a shared contract - You need to validate technical feasibility before committing to a PRD - You want to catch design issues early — before code is written --- ## The Job 1. **Locate PRD** — find or receive the PRD document 2. **Analyze context (optional)** — if a codebase exists, scan it to understand current architecture, patterns, and constraints 3. **Ask clarifying questions** — resolve technical ambiguities (max 3-5 questions) 4. **Generate SPEC** — produce a structured technical specification 5. **Review** — present to user for feedback and iteration 6. **Save** — write final SPEC to agreed location --- ## Step 1: Locate PRD Find the input PRD in one of these ways: ``` Provide the PRD to convert: A. File path (e.g., tasks/prd-priority-system.md) B. GitHub Issue URL C. Paste PRD content directly D. Auto-detect: scan tasks/ directory for recent PRDs ``` If auto-detecting, list available PRDs and let the user choose: ``` Found PRDs in tasks/: 1. tasks/prd-priority-system.md (2024-03-15) 2. tasks...