validate-specslisted

# Transmute — Specification Validation (Stage 2B) Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/validate-specs-detailed-guide.md` for the complete validation procedures, teammate spawn prompts, and report templates. ## Prerequisites Before starting, verify: 1. `./plancasting/brd/` directory exists and contains markdown files. If missing, STOP: "Stage 2B requires completed BRD (Stage 1). Run Stage 1 first." 2. `./plancasting/prd/` directory exists and contains markdown files. If missing, STOP: "Stage 2B requires completed PRD (Stage 2). Run Stage 2 first." 3. `./plancasting/tech-stack.md` exists. If missing, STOP: "Stage 2B requires `plancasting/tech-stack.md` from Stage 0. Run Stage 0 first." ## Purpose Independently cross-validate the BRD and PRD for consistency, completeness, and correctness — catching errors before they propagate into code. The BRD and PRD are generated by separate Agent Team sessions, so several categories of errors can slip through: - BRD requirements overlooked or misinterpreted during PRD generation - PRD specifications that contradict BRD constraints - Terminology inconsistencies between documents - Missing user stories for functional requirements - Screen specs that don't match user flow descriptions - API specs that don't cover all screen data needs - Untestable acceptance criteria - Cross-feature interactions documented in BRD but missing from PRD Fixing these now costs minutes. Fixing them after code is written costs hours. ##