executing-plans

To execute an implementation plan with checkpoints and branch safety, provide the absolute plan path, and the workflow enforces verification gates, per-step checkbox tracking, and feature branch isolation before running tasks.

Tracking implementation plan progress with checkboxes and commit policies requires per-step checkbox updates immediately after task verification, ensuring no status drift and strict adherence to the plan's defined commit policy.

Spec compliance review during plan execution works by running structured reviewers in a specific order, retrying reviews up to a defined budget before escalating, ensuring both spec compliance and code quality are verified.

You cannot run plan execution directly on the main branch without hitting a safety gate; the workflow enforces branch safety by recommending feature branches or isolated worktrees before executing any implementation steps.

Executing a multi-step feature plan reads and follows the specific commit policy defined in your plan file, including strict no-commit policies, without guessing, to ensure branch safety and structured review compliance.

Implementation plan execution fails before starting tasks if plan_path validation or branch safety checks fail, preventing accidental commits to main or executing steps without proper feature branch isolation and verification gates.