executing-plans

Batch-executing a plan with checkpoints involves loading a structured plan file, performing critical reviews, executing tasks in controlled batches, tracking per-task statuses, and generating post-batch reports for feedback before proceeding to the next batch.

The best way to safely implement a structured plan is to execute tasks in controlled batches with built-in verifications and review checkpoints. This approach reduces risk by generating post-batch reports and requiring feedback before continuing to the next set of tasks.

You track task-status during multi-step plan execution by applying per-task statuses like in_progress and completed within each batch. The execution process includes built-in verifications to ensure accountability before advancing to subsequent tasks.

You need a structured plan file format, such as YAML, to load a plan for batch execution. The file must contain the task definitions necessary for the system to perform critical reviews, execute batches, and generate status reports.

You can optionally invoke the finishing-a-development-branch sub-skill for final validation and release readiness after completing all plan batches. This integration ensures the executed tasks meet final verification standards before release.

You should not use batch execution with checkpoints for simple, single-step tasks that do not require risk mitigation or feedback loops. This structured execution process is designed for multi-step plans where accountability and verification are critical.