executing-plans

Executing a development plan in batches involves loading a plan file, processing tasks in default groups of three, running verifications, and generating progress reports between batches to enforce review checkpoints. You can prompt for blockers before continuing to the next batch.

Staged execution for project management plans is a process that divides work into isolated sessions with decision points. It applies documented plans to projects requiring risk review before continuing across batches, ensuring blockers are surfaced.

To load a plan file and track task status, initiate the execution skill to perform a critical review for gaps, then mark task statuses as you run verifications. The system reports results between batches to keep tracking aligned.

The default batch size for running a plan is 3 tasks, which enforces review checkpoints and surfaces blockers. You process these batches in isolated sessions, generate progress reports, and enable user prompts for questions before continuing.

Plan execution integrates with git worktrees to coordinate staged execution in isolated sessions. It works alongside writing plans and finishing development branches to manage batch execution, risk review, and decision points.