executing-plans

To execute a development plan with verifications and checkpoints, load the written plan, critically review the tasks, and drive progression with explicit status updates and controlled verifications to ensure reliable delivery.

The best way to coordinate end-to-end implementation of an approved design is to load the written plan and execute tasks sequentially with subagents, applying review checkpoints to validate each step of the development workflow.

Yes, you can use git-worktrees to manage tasks while executing a plan by integrating with related skills to isolate development branches and perform final validation during the development workflow.

Yes, you need a written plan before starting the execution workflow, because the process requires loading an existing, approved design to critically review and drive the tasks to completion with guardrails.

Subagents fit into the development workflow by coordinating with the plan execution skill to ensure end-to-end delivery, handling specific tasks while the main process maintains review checkpoints and quality checks.

You should not use an automated plan execution workflow if you lack an approved design or a written sequence of tasks, as the process critically reviews and loads existing plans to drive verifications and controlled progression.