implementing-plans

Phase-based execution divides your plan into discrete stages, running each with built-in verification criteria before pausing for human review. After each phase completes, the Skill validates success criteria, updates plan checkboxes, and waits for approval to proceed to the next phase.

When verification detects a mismatch between expected and actual outcomes, the Skill pauses execution and surfaces the discrepancy for human review. You can then decide whether to continue, adjust the plan, or restart the phase.

Yes. Phase-based implementation with explicit verification criteria is designed for feature rollouts requiring sequential execution, automated validation (tests, linting, type checking), and manual approval gates between phases.

The Skill enforces success criteria checks after each phase completes. It compares actual execution results against defined criteria, then updates plan checkboxes and notifies you whether the phase passed or requires attention before advancing.

Automated verification includes tests, linting, and type checking. These run after each phase to validate outcomes. Human verification pauses occur when the Skill detects mismatches, giving you explicit control over advancing to the next phase.