executing-plans

Batch plan execution loads a written plan and runs tasks in controlled batches with verification checkpoints between them. It progresses deterministically, executing the first three tasks per batch by default, tracking status as in_progress and completed, and prompting for feedback before continuing.

Batch task tracking monitors task progression through staged workflows by executing groups of tasks sequentially. It reviews the plan critically, marks tasks as in_progress or completed, performs verifications at each checkpoint, and prompts for feedback to ensure controlled execution.

Yes, batch execution with checkpoints requires a plan file to be loaded first. The workflow critically reviews the written plan before executing tasks in controlled batches, making a pre-defined plan an essential prerequisite for staged verification and feedback loops.

Batch execution applies to plan-driven workflows across development, operations, and instruction-following tasks. Any staged workflow requiring controlled progression, critical review between batches, and checkpoint verification can use this batch execution approach.

Task progression is controlled deterministically by executing three tasks per batch by default, pausing for verification and feedback at each checkpoint. This produces audit-ready reporting with in_progress and completed status tracking throughout the execution lifecycle.

Batch execution with checkpoints is limited to plan-driven workflows and requires a loaded plan file to function. It processes a fixed batch size of three tasks by default, meaning users cannot dynamically resize batches without adjusting the workflow configuration.