What problem does it solve? Multi-phase AI agent workflows often close phases without verified evidence, leading to undocumented changes, undetected spec drift, hallucinated APIs, and untested code shipping silently. This Skill enforces a deterministic closeout protocol that blocks phase completion until all required evidence artifacts exist. ## Core Features & Use Cases - Mandatory Retrospective Gate: Writes a structured retrospective bundle (task counts, rejections, test failures, lessons learned) to .swarm/evidence/ before phase_complete can succeed. - Verification Gates: Runs drift verification against spec.md, hallucination checks on changed files, mutation testing, and SBOM generation, each enforced by runtime hooks that block phase_complete when evidence is missing. - Council Reviews: Dispatches 5-member phase and final councils (critic, reviewer, SME, test engineer, explorer) whose verdicts gate the last phase of a plan. - Use Case: An architect agent finishing Phase 2 of a coding plan uses this protocol to rescan the codebase, update docs, record retrospective metrics, verify no drift from the spec, and only then call phase_complete. ## Quick Start Ask the architect agent to wrap up the current phase and run the full phase-wrap protocol before completing it.
