executing-plans

Batch-based plan execution automates implementing written plans by processing tasks in controlled batches with in_progress and completed statuses. It pauses after each batch to report results and await feedback before continuing to the next set of tasks.

Blocker handling in plan execution stops the current batch workflow and raises issues through structured reporting. The process awaits feedback and issue resolution before resuming task execution, ensuring development stays controlled and auditable.

Plan execution integrates with version control workflows including git-worktrees to manage batch-based task implementation. This allows controlled development across isolated branches while maintaining verification and review checkpoints between each batch.

Task verification occurs automatically after each batch execution step. The workflow enforces verification checks and reports batch results with in_progress and completed statuses before prompting for review and allowing the next batch to proceed.

Plan execution enforces plan loading and critical review before any tasks begin. It reads the written plan, raises questions or concerns about the proposed development workflow, and only starts executing the first batch of three tasks after review.

Batch-based execution is not suited for unstructured or ad-hoc development work lacking a written plan. It requires a detailed plan file to load and review, enforcing structured batch execution, verification, and guardrails that may constrain rapid prototyping workflows.