executing-plans

To execute a plan in batches, load your plan file, review it critically, and process the first three tasks by marking them in_progress, performing steps, running verifications, and marking completed. After each batch, generate a report and request feedback before continuing.

Batch-based workflow execution is a structured approach processing project tasks in groups with explicit checkpoints. It enforces in-progress state tracking, per-task verifications, and batch-end reporting to support iterative development cycles and staged delivery.

Yes, batch task execution supports software development sprints, research tasks, and comprehensive documentation efforts. Any predefined plan requiring staged delivery with iterative reviews and structured reporting can utilize this batch-based workflow.

Batch execution tracks task states by marking tasks in_progress, performing steps exactly as written, running verifications, and marking completed. This ensures structured tracking and verification per task before generating a batch-end report.

Yes, you need a predefined plan file loaded into the session. Review it critically and raise concerns before starting, as batch execution processes tasks exactly as written from the plan with verifications and batch-end reporting.

Yes, batch plan execution provides optional integration hooks to other skills. It includes structured reporting and feedback hooks to support iterative development or QA cycles across software projects, research tasks, and documentation efforts.