executing-plans

Implementation plan execution is automated by loading a written plan, reviewing it critically, and executing tasks in default batches of three with verification checkpoints. The workflow runs verifications after each batch, reports results for review, and pauses on blockers to request explicit guidance before continuing.

Batch-based plan execution is a structured workflow that processes written implementation tasks in staged increments with periodic review. It is needed for incremental development projects requiring staged task execution, verification, and traceability across teams to prevent ad-hoc execution errors.

Verifications run automatically after each batch of tasks is executed, generating a progress report for review. The system stops on blockers, requests clarifications, and continues only with explicit guidance to ensure quality and traceability are maintained before the next batch.

Git worktrees integrate with batch task execution as a prerequisite for staged development. The workflow coordinates plan execution across development branches, using worktrees to isolate batch tasks, run verifications, and manage checkpoints before merging the finished branch.

Plan execution across teams is coordinated by loading a shared plan, reviewing it for concerns, and executing tasks in batches with progress tracking. The workflow surfaces questions through review checkpoints, stopping on blockers to request clarifications and ensure delivery stays aligned.

Batch execution stops after completing tasks to enforce review checkpoints and run verifications. This mechanism surfaces blockers, requests clarifications, and requires explicit guidance before continuing, ensuring structured auditability and preventing ad-hoc execution errors from propagating.