pm-closure-validation

Increment closure validation enforces a 3-gate quality process: verify task completion across priority levels (P1-P3), confirm test coverage and passing results, and ensure documentation updates (CLAUDE.md, README, CHANGELOG). Use /done to trigger the validation flow and receive a formal closure verdict with pass/fail status.

The 3-gate validation assesses task completion status, test passing and coverage metrics, and documentation updates. It also detects scope creep and requires PM approval, outputting actionable remediation guidance if any gate fails.

The Skill evaluates increment context loaded from spec.md, plan.md, and tasks.md against gate criteria. Scope creep detection identifies work outside the planned increment and flags it during closure validation to prevent unapproved expansion.

Gate 3 requires updates to CLAUDE.md, README, and CHANGELOG. These documentation updates ensure accurate records of changes, decisions, and release notes before increment closure approval.

Yes. Gate 1 assesses task completion across P1 (critical), P2 (high), and P3 (standard) priority levels, allowing validation of increments containing mixed-priority work before PM approval and closure.

The validation outputs a fail status with actionable remediation guidance. You must address the failed gates—incomplete tasks, insufficient test coverage, or missing documentation—before resubmitting for PM approval and closure.