executing-plans

To execute an implementation plan with task tracking, load the plan, review it for gaps, and iterate through tasks with in_progress and completed states. The workflow enforces checkpointing by running specified verification steps for each task before proceeding.

When a blocker requires an immediate stop during plan execution, the workflow pauses to ask for clarification instead of guessing. It forces a safe stopping point and prevents claiming work is done until verification passes and the blocker is resolved.

To ensure release readiness in a software development workflow, follow the plan's bite-sized steps exactly and run the specified verifications for each task. Final completion requires delegating the finishing work to verify integration choices.

Yes, this plan execution workflow supports TDD-friendly plans by applying task-by-task execution with explicit checkpoints. It reads the plan first, flags gaps or concerns, and runs the specified verification steps to ensure testing aligns with the plan.

To manage development branches when completing a plan execution workflow, delegate final completion to the finishing-a-development-branch skill. This ensures integration choices are verified and the branch is safely completed after all task checkpoints pass.

Yes, you can use this task tracking workflow if your plan has gaps. It critically reviews the plan first, flags any concerns or missing steps, and pauses to ask for clarification instead of guessing how to proceed with the execution.