What problem does it solve? Translating a Business Requirement Document into a complete, engineering-ready PRD is slow and error-prone, often producing gaps in traceability, missing error states, and inconsistent specifications across features. ## Core Features & Use Cases - Multi-Agent PRD Generation: Spawns five specialized agent teammates covering product strategy, user stories, screen specifications, API and technical architecture, and quality/operations to produce 18 numbered PRD files. - Full Traceability and Coverage Audits: Builds a Feature Decomposition Map linking every BRD requirement (BR/FR/NFR) to epics, user stories, screens, and API endpoints, with structural consistency and dependency-cycle validation. - Quality Review and Remediation: Runs completeness, consistency, and technical review agents, then remediates CRITICAL and HIGH findings with a logged review trail. - Use Case: After completing Stage 1 (BRD) of the Transmute pipeline, run Stage 2 to produce a full PRD in ./plancasting/prd/ with user stories, screen specs, API schemas, and a testing strategy ready for Stage 3 scaffolding. ## Quick Start Ask the assistant to generate the PRD from the BRD by running Stage 2 of the transmute pipeline.