executing-plans

Executing a development plan with safety stop conditions involves reading the plan, verifying understanding, and processing bite-sized steps with review checkpoints. The workflow immediately stops on blockers, missing dependencies, or repeated verification failures to prevent costly guessing.

Checkpointed workflow task verification is a process that executes written implementation plans step-by-step, running specified verifications at each stage. It tracks progress across multiple subtasks and enforces explicit stop conditions when tasks fail verification or encounter unclear instructions.

To automate step-accurate task execution, load the implementation plan and perform a critical initial review, escalating questions to a human partner. Then execute each decomposed task exactly as planned, marking states and running the specified verifications until completion.

Checkpointed workflows for development automation require a precise, written implementation plan as input. Without a pre-written plan decomposed into bite-sized steps, the workflow cannot perform its critical initial review or execute the step-accurate tasks with verification gates.

Plan execution stops immediately on verification failures to enforce fail-fast guardrails and prevent costly guessing. When blockers, missing dependencies, or repeated test completion failures occur, the workflow halts to avoid compounding errors across subsequent subtasks.

Yes, completing plan execution requires a mandatory handoff to the finishing-a-development-branch workflow. This required wrap-up step verifies tests and presents final options, ensuring development tasks are fully validated before completion.