executing-plans

To execute a written plan end-to-end, load the plan, review it for ambiguities, execute each task with verifications, halt on blockers, and trigger final completion workflows. This ensures structured execution with traceable task progression.

Plan-driven execution is automating a written plan from review to completion with built-in verifications. It prevents missed checkpoints and miscommunications by halting execution when blockers are encountered, ensuring every task is verifiably complete.

When handling blockers during plan execution, the workflow halts automatically and requests guidance. This stop-for-blockers mechanism prevents unchecked errors and ensures tasks are not marked complete without resolving the blocking issue.

Yes, using git-worktrees is required to manage isolated workspaces during plan execution. It works alongside writing-plans and finishing-a-development-branch sub-skills to handle plan creation, isolated development, and final branch verification.

Yes, you can import an existing plan to review and surface concerns before execution. The loading and review process identifies ambiguities in the written plan, ensuring tasks are clearly defined before structured execution begins.

The best way to trace task progression is to use a structured execution workflow that applies explicit status updates and built-in verifications to each task. It traces tasks from initial review to finishing a development branch.