executing-plans

Batch execution of an implementation plan involves running tasks sequentially, updating their status, and pausing between batches for verification reporting and human feedback before continuing. This Skill loads your plan, reviews it critically, and blocks execution if concerns remain unresolved.

Preventing architectural drift during project coordination requires executing written plans in bite-sized batches with explicit checkpoint reviews and interim reporting between task groups. This approach enforces a review loop where an architect verifies implemented work before subsequent tasks proceed.

Pausing development workflow execution for human feedback is supported through a checkpoint reporting system that stops after each batch. It reports implemented work and verification output, then resumes task iteration based on the provided feedback.

When task verification fails repeatedly during plan execution, a safe stop-and-ask policy activates to pause the workflow. This blocker policy prevents continuing flawed batch execution and requires human intervention to resolve the verification failure.

Batch execution supports deterministic iteration with task status tracking by marking items as in_progress or completed. It follows plan steps precisely, running specified verifications per task to ensure deterministic batch execution and accurate status reporting.