executing-plans

Plan execution works by loading a written plan, critically reviewing it for risks, and driving tasks in sequence with status tracking and verifications. It creates a TodoWrite to monitor progress and performs formal checkpoints after each step.

The best way to track task status during structured plan execution is using a TodoWrite to monitor each step. The workflow updates statuses sequentially, performs verifications for completed tasks, and maintains formal checkpoints throughout the development process.

Reviewing a written development plan for risks involves loading the plan file and critically evaluating its contents to identify questions and potential issues before execution. This pre-execution phase ensures risks are mitigated before driving tasks in sequence.

Yes, you can use git-worktrees with a stepwise plan execution workflow. The execution process supports development contexts using git-worktrees, allowing isolated task execution, verification, and structured handoffs to finishing workflows upon completion.

To transition to a finishing workflow after development tasks complete, execute all plan steps with verification checkpoints until statuses are complete, then trigger a structured handoff. This supports downstream processes like finishing a development branch.