Gatekeeper Skill

Phase transition validation automatically checks prerequisites, artifact completeness, and quality criteria at each workflow stage—Vision, Stack, Plan, Feature, Build, Code, and Done—ensuring all gates are satisfied before progression. Invoke the Gatekeeper with /gate validate [phase] to scan for gaps, placeholders, and standard violations, receiving detailed reports with severity levels to guide remediation.

Quality gates enforce Object Calisthenics, SOLID principles, design patterns, and custom quality rules across all phase transitions. The Skill checks artifact existence, completeness, alignment with specifications and project constitution, detects TODOs and TBDs, validates mandatory fields, and identifies broken references, providing objective feedback at each gate.

Yes. Automated quality checks scan for placeholders, outdated dates, empty fields, and specification misalignment, delivering immediate feedback on identified gaps with actionable recommendations. This ensures deterministic workflow progression and prevents low-quality or incomplete artifacts from moving to the next phase.

After completing the Stack phase, invoke the Gatekeeper to automatically verify that all ADRs are complete, constraints are properly documented, and solution strategy is sound. The Skill reports completeness status and quality adherence, blocking progression until all Stack-phase prerequisites are satisfied.

The Gatekeeper delivers detailed reports classifying issues by severity—Critical, High, Medium, Low—with specific gaps identified and correction recommendations. Your project remains at the current phase until you resolve flagged issues and revalidate against the gate criteria.

Yes. Validation applies comprehensively across Vision→Stack, Stack→Plan, Plan→Feature, Feature→Build, Build→Code, and Code→Done transitions, checking phase-specific prerequisites and artifacts while enforcing consistent quality standards, architectural patterns, and compliance rules throughout the entire project lifecycle.