executing-plans

Executing a development plan step-by-step involves loading the written plan, reviewing it critically, and processing tasks sequentially while enforcing verification checkpoints at every stage to ensure accuracy. The workflow stops automatically if blockers arise during execution.

Plan-driven task execution is an automated workflow that reviews and processes written plans sequentially. You need an isolated workspace, such as git-worktrees, when executing development tasks to keep checkpoints and verifications separated from your main environment.

Yes, you can use this plan execution workflow for data and operational tasks. It applies to any plan-driven workflow requiring clear steps, checkpoints, and verifications, successfully completing tasks across development, data, and operational domains.

The best way to automate end-to-end plan execution is by using sub-skills to load, review, and execute written plans. This approach confirms a completion workflow by applying verifications and checkpoints to each task step-by-step.

To handle blockers when executing a multi-step plan, the workflow stops execution immediately upon encountering an issue. It enforces verification checkpoints at every step, ensuring you review the blocker before proceeding with the remaining tasks.