executing-plans

Plan execution with step-by-step verification is managed by loading a written implementation plan and processing tasks sequentially within an isolated workspace. The workflow enforces review checkpoints to identify gaps before proceeding to the next task.

Blocker handling during feature rollouts is structured through critical review loops that identify gaps and decision points. The execution workflow pauses progress at checkpoints to assess blockers before safely continuing with subsequent development tasks.

Yes, an explicit written implementation plan is required. The workflow orchestrates task execution by loading an existing plan, reviewing it for gaps, and applying continuous verifications until completion rather than generating the plan itself.

Plan execution in a separate session is supported to isolate development workspaces and ensure safe completion. This architecture leverages sub-skills like git worktrees to manage isolated environments during step-by-step task processing.

Checkpoint review loops in development sprints work by validating task completion and identifying gaps before allowing progression. The workflow enforces these critical review points between tasks to ensure structured progress and safe branch completion.

Executing plans without structured checkpoints limits the ability to identify gaps and handle blockers before proceeding. Without enforced review loops, step-by-step verification is bypassed, increasing the risk of unmanaged decision points during complex development workflows.