prdlisted

# Transmute — PRD Generation (Stage 2) Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/prd-detailed-guide.md` for the complete agent team architecture, teammate spawn prompts, token budget management, review agent checklists, story grouping examples, and writing guidelines. ## Prerequisites Before starting, verify: 1. `./plancasting/brd/` directory exists and contains markdown files. If missing or empty, STOP: "Stage 2 requires completed BRD (Stage 1). Run Stage 1 first." 2. `./plancasting/tech-stack.md` exists. If missing, STOP: "Stage 2 requires `plancasting/tech-stack.md` from Stage 0. Run Stage 0 first." ## Critical Framing This PRD uses the **Full-Build Approach**: the COMPLETE product is built and launched as a single release. No MVP, no phased rollout, no feature deferral. P0-P3 priorities define dependency order for parallel development, NOT which features to include or exclude. ALL features ship. ## BRD → PRD Relationship The BRD defines WHAT the business needs. The PRD defines WHAT the product must do and HOW it should behave. Every PRD element must trace back to one or more BRD requirements. The PRD must be detailed enough for engineering, design, and QA teams to begin work without ambiguity. ## Execution Flow ### Step 1: Read and Analyze Inputs Read and fully internalize: - All files in `./plancasting/brd/`, including `_context.md` - All files in `./plancasting/businessplan/` for additional context - `./plancasting/tech-stack.md` for stack-in