executing-plans

Batch execution runs a default first set of tasks (e.g., first 3) with per-task progress updates, pauses for verification and review, then continues to the next batch. Load your plan file, execute the initial batch, report results, await review feedback, then proceed iteratively through remaining tasks with documented checkpoints between each batch.

Structured batch processing applies verification checks after each group of tasks completes. This approach marks task statuses (in_progress, completed), produces verification outputs and review-ready reports, and supports blocker escalation through a dedicated follow-on sub-skill, ensuring critical steps are validated before advancing.

Yes. The Skill loads plan files, executes tasks sequentially in bite-sized batches, tracks per-task status markers, generates verification outputs and review documentation after each batch, and handles blockers with escalation support, enabling structured implementation of externally-provided plans.

Use batch execution when tasks require critical plan review, sequential verification between groups, and documented reporting. It suits development implementations and operational workflows where stakeholder sign-off between task batches is necessary and bite-sized progress tracking improves visibility.

The Skill includes dedicated blocker handling and escalation via a follow-on sub-skill. When execution encounters obstacles, blockers are flagged, documented in review reports, and escalated through the sub-skill for resolution before proceeding to the next batch.