executing-plans

Automating implementation plan execution requires loading a written plan and processing each step sequentially with review checkpoints. This skill manages task progression from loading and critical review to execution, verification, and completion reporting.

Ensuring development workflow steps are followed precisely involves using automated plan execution with built-in critical review checkpoints. This approach marks tasks as in progress, runs specified verifications, and reports completion to maintain development consistency.

Running verification steps automatically after task completion is a core feature of plan execution workflows. The skill ensures specified verifications are executed after each task is marked completed, reducing errors and validating code implementation.

Plan execution workflows handle critical review checkpoints by prompting for plan review before execution begins and allowing users to revisit steps. This mechanism ensures the written implementation plan is validated before code implementation proceeds.

A written implementation plan file is required to start automated task management. The skill loads the plan document, such as a markdown file, to extract the defined steps and execute the development workflow with verification.

Automated plan execution should not be used when a development workflow lacks defined steps or specified verifications. Without a detailed written implementation plan, the skill cannot properly manage task progression or run review checkpoints.