phase-wrap

To enforce mandatory phase completion in AI-led development workflows, you need a gating protocol that blocks closure until retrospective evidence, quality checks, and council reviews are collected. This Skill coordinates evidence collection, drift verification, and mutation testing before allowing phase advancement.

A retrospective evidence gate for phased software development is a mandatory checkpoint that blocks phase closure until a complete evidence bundle capturing phase metrics, lessons learned, and rejection reasons is written for continuous improvement.

You can prevent hallucinated APIs and spec drift during phase closure by running conditional quality gates that verify implementation against project specs and check for fabricated APIs. This protocol applies drift and hallucination verification before allowing phase progression.

Phase closure requires mutation testing to pass before proceeding when enabled in the QA gate profile. This protocol automatically runs mutation testing for test coverage alongside drift verification and council reviews to satisfy production-grade quality assurance requirements.

You can use this quality gate protocol with OpenCode Swarm multi-phase implementation plans. It automates enforcement of all required closure steps for OpenCode Swarm users, ensuring no phase proceeds without passing all configured validation checks.

Your phase closure gets blocked without required agent delegations because this gating protocol satisfies production-grade quality assurance requirements by blocking incomplete phase closures that lack required evidence, agent delegations, or passing quality gate verdicts.