executing-plans

Batch execution processes a written implementation plan in staged groups, tracking progress and stopping for review feedback after each batch completes. This ensures scope control and incremental verification before proceeding.

Critical plan review reads the implementation plan first and flags gaps, blockers, or unclear instructions before coding begins. This validation step prevents wasted effort on ambiguous or incomplete task specifications.

Isolated worktree setup creates a separate workspace for batch execution, keeping implementation changes isolated until verification passes. This structured development-branch workflow integrates with finishing workflows for safe branch completion.

Feedback checkpoints stop execution after each batch of tasks, report results, and wait for your review before continuing. This repeated feedback loop ensures quality control throughout multi-step refactoring or development work.

Task tracking during batch execution monitors completed and pending tasks within each staged group, providing structured progress reports at review checkpoints. This prevents scope drift and maintains implementation plan alignment.

Batch-based execution is not suited for single-step tasks or trivial changes that require no review checkpoints. It is designed for multi-step development work needing critical validation, incremental coding, and repeated feedback loops.