executing-plans

Executing an implementation plan with checkpoints involves breaking the code implementation into manageable batches, completing each batch, and prompting for critical review between stages to ensure the final development workflow meets requirements.

Batch execution automates the progression of pre-defined implementation plans, completing manageable task groups, performing verifications, and prompting for critical human review between stages to maintain quality and alignment.

Yes, you need a written implementation plan before starting batch execution, as the structured task management process requires pre-defined steps to adhere to during development. You provide a file like 'implementation_plan.md' to initiate the workflow.

Yes, you can use git worktrees when executing plans, as the execution workflow integrates with git worktree management to isolate development branches while running batch executions and reporting progress at checkpoints.

Checkpoint reporting pauses the execution of an implementation plan after a batch of tasks, performs verifications, and outputs a progress report that awaits human feedback before continuing to the next development stage.

You should use batch execution for complex feature implementation to prevent overwhelm, allow focused work on manageable task groups, and ensure critical review checkpoints catch alignment issues before moving to the next stage.