executing-plans

Batch execution processes tasks in groups, marking each as in_progress or completed, then pausing for review checkpoints. This verification-first workflow catches architectural issues early by validating specified checks between iterations before continuing.

A verification-first workflow in agentic coding follows each plan step precisely and runs specified verifications rather than skipping checks. It requires critically reviewing the plan, executing tasks in batches, and pausing for feedback before continuing.

You track task completion status by marking tasks as in_progress or completed during batch execution. The workflow reports results between batches for review, ensuring each task is followed exactly and verified before moving to the next iteration.

Yes, the workflow pauses for feedback between task batches. It executes a default batch of the first three tasks, reports results at a checkpoint, and waits for your feedback before continuing to the next iteration.

After completing and verifying all tasks, the workflow hands off to a required finishing skill for final validation and decision-making. This ensures executed work undergoes final review before the overall plan is considered fully complete.