executing-plans

To execute a software development plan, load the written plan, review it critically for concerns, and execute all tasks deterministically in sequence with status tracking and verifications. Structured checkpoints ensure safe, auditable progress throughout the workflow.

The best way to review an implementation plan is to load the written plan and critically assess it for concerns before executing any tasks. This human-in-the-loop checkpoint validates the development workflow and ensures tasks are safe to execute sequentially.

Yes, you need git worktrees to ensure safe, auditable progress when executing plans. The workflow requires git worktrees alongside task tracking tools to manage isolated branches and validate changes during development.

Task tracking works by using TodoWrite to monitor the status of every task executed in sequence. As the plan executes deterministically, status updates and structural checkpoints report progress and validate changes made during development.

Yes, you can use subagents to validate changes during plan execution. The workflow coordinates with required workflow skills, deploying subagents where available to verify modifications and ensure auditable progress before moving to the next task.

You should not use an automated plan execution workflow when a project lacks a written implementation plan or requires no human-in-the-loop decisions. The workflow critically depends on pre-written plans and structured checkpoints to guide task execution and verifications.