What problem does it solve? Business Requirements Documents and Product Requirements Documents are often generated in separate sessions, causing terminology drift, missing requirement coverage, broken cross-references, and untestable acceptance criteria that become expensive bugs once code is written. This Skill catches those specification errors before they propagate into implementation. ## Core Features & Use Cases - Requirements Traceability: Builds a forward and reverse traceability matrix mapping every BRD functional requirement (FR-xxx) to PRD user stories, screen specs, and API specs, flagging coverage gaps and orphan stories. - Consistency & Quality Validation: Three parallel validation teammates check terminology, data models, user flows, API-to-screen alignment, acceptance criteria testability, and technical feasibility against the chosen tech stack. - Automated Fixing & Gate Decision: Fixes CRITICAL and HIGH severity issues directly in the BRD/PRD files, then produces a health-scored report with a PASS / CONDITIONAL PASS / FAIL gate decision for Stage 2B of the Transmute pipeline. - Use Case: After generating a BRD and PRD for a new SaaS product, run Stage 2B to discover that three P0 requirements lack API specs and that the PRD weakened a quantified uptime target — then have those issues fixed in place before scaffolding begins. ## Quick Start Ask the agent to validate specs and cross-check the BRD and PRD in the plancasting directory for coverage gaps and contradictions.
