executing-plans

Batch execution divides your implementation plan into manageable groups (default 3 tasks per batch), executes them sequentially, then enforces verification gates before proceeding to the next batch. This maintains quality and prevents cascading failures across your entire plan.

Task statuses are enforced per-task as either in_progress or completed, providing clear visibility into which tasks are active and which have finished. This standardized tracking enables accurate progress reporting and helps identify blocked or stalled work.

Yes, the Skill includes built-in stopping criteria that let you pause execution before moving to the next batch. Verification gates after each batch provide the checkpoint to assess outcomes and decide whether to continue, adjust, or halt.

Standardized batch reporting summarizes outcomes, status changes, and verification results after each batch completes. This feedback loop integrates findings into the next cycle, enabling iterative refinement of your execution plan.

Yes, your plan must be ready for implementation before you start. The Skill takes a structured plan as input and guides you through batch execution, verification, and reporting—it doesn't create or validate the plan itself.