executing-plans

To execute a development plan with review checkpoints, load the written plan in a separate session, track explicit task states, perform stepwise verifications, and pause for stakeholder review before completing the branch.

Task verification in plan-driven development is the process of validating explicit task states against a loaded plan, ensuring stepwise execution meets requirements before advancing to subsequent development workflow stages.

Track progress against a written software development plan by using a plan loader to enforce explicit task states, updating statuses sequentially, and triggering verifications at predefined review checkpoints.

Yes, you can surface risks and questions before executing a development plan by critically reviewing the loaded plan in a separate session to ensure alignment and quality prior to stepwise task execution.

Executing a planned task can integrate subagents and sub-skills like finishing-a-development-branch to apply guardrails and finalize work, though core execution primarily requires a plan loader and explicit task states.