executing-plans

Execute plans by breaking them into small batches (typically 3 tasks per batch) with mandatory review checkpoints between each batch. Complete tasks, verify results, report progress, gather feedback, then proceed to the next batch until the plan is finished.

Review the complete plan upfront to surface concerns, then execute in staged batches with architectural validation at each checkpoint. This staged approach ensures each development phase aligns with the original design before proceeding further.

Mark each task with status tracking (in_progress, completed), report verification output after each batch completes, and document human feedback at every checkpoint. This creates an auditable record of what was built and validated at each stage.

Yes. Stop immediately if blocked, report the blocker with context, and wait for feedback before proceeding. The staged execution model ensures blockers are caught early rather than compounding through multiple batches.

Use the finishing-a-development-branch workflow to complete the development branch once all plan batches pass their checkpoints. This transitions the staged implementation into final, merged code.