What problem does it solve? Development phases often move forward without independent quality gates, letting defects and non-compliant deliverables slip through. This Skill enforces a mandatory review gate for every /dev phase, ensuring a different reviewer validates outputs before the workflow advances. ## Core Features & Use Cases - Phase-based reviewer assignment: Maps each phase (requirements, prd, architecture, stories, database, backend, frontend, testing, review, deployment) to a designated reviewer distinct from the author. - Checklist-driven reviews: Applies document, code, testing, or deployment review checklists from the references directory based on the current phase. - Automated validation and blocking: Runs phase-specific validations (e.g., ruff and pytest for backend) and blocks progression on CRITICAL or HIGH findings, persisting reports to docs/reviews/. - Use Case: After completing the backend phase, run the review gate to execute lint and test checks, verify textbook compliance, and generate docs/reviews/phase-06-backend.md before updating .dev-state.yaml. ## Quick Start Ask the AI to run the phase review gate for the current development phase and generate the review report.
