phase-checkpoint

Automate phase verification by executing the Phase Checkpoint criteria defined in EXECUTION_PLAN.md to run required tests, linting, security scans, and production checks before advancing. This ensures all acceptance criteria are satisfied automatically.

A phase checkpoint is an automated validation step that verifies all required tests, lint, type checks, security scans, and manual verifications are completed in a project phase before moving to the next step. It enforces quality gates defined in EXECUTION_PLAN.md.

Yes, phase checkpoint verification requires a local configuration file at .claude/verification-config.json along with the EXECUTION_PLAN.md file. These files determine the specific checks to run for greenfield or feature phases.

Validate acceptance criteria by running the phase checkpoint command with the specific phase number to execute all required tests, linting, type checks, and security scans defined in the execution plan. It confirms readiness to advance.

Yes, phase checkpoints determine auto-advance readiness by validating all acceptance criteria and optionally triggering the next phase. It reads project configuration to tailor verification steps for greenfield or feature contexts.

Phase checkpoint verification fails when required tests, lint, type checks, security scans, or manual verifications defined in EXECUTION_PLAN.md are not completed. Ensure .claude/verification-config.json is present and all criteria pass before advancing.