executing-plans

Batch plan execution loads a written plan, validates it, and executes tasks in groups of three with human review checkpoints between batches. It tracks in_progress and completed statuses, runs verifications, and produces structured reports for partner feedback before proceeding.

Task tracking during staged deployment uses TodoWrite to mark each task as in_progress, follows exact plan steps, runs specified verifications, and marks tasks completed. This maintains auditable status records and produces verification results for review before advancing to the next batch.

Batch processing with review checkpoints prevents drift by enforcing exact plan steps and requiring human partner review of implemented work and verification results between batches. This controlled execution reduces miscommunication and ensures the plan is followed precisely before continuing.

Yes, batch execution with checkpoints applies to project execution sessions across development, planning reviews, and staged deployments. It validates the plan, executes tasks in batches, and requires review feedback at each checkpoint before proceeding to subsequent batches.

After the final batch is completed and verified, the execution announces completion and optionally triggers a follow-up sub-skill like finishing-a-development-branch per the plan. This signals that all development work is done and downstream actions can proceed.

During plan validation, you should examine the plan file, identify any questions or concerns, and raise blockers with your human partner if needed. Plan execution only begins after the plan is approved and any blockers are resolved.