executing-plans

Executing a written implementation plan step by step requires deterministic task execution that marks items in progress and completed while running specified verifications. The skill enforces strict sequential execution and a critical upfront review before starting any tasks.

The best way to track progress during workflow orchestration is by marking bite-sized planned tasks in progress and completed sequentially. This enforces mandatory review checkpoints and task verifications before safely handing off to a completion workflow.

STOP-on-blocker behavior immediately halts plan execution when a blocker or failing verification is encountered. This prevents wasted effort during task execution by forcing a complete stop until the human partner addresses the blocker or answers surfaced questions.

Yes, you need a previously written implementation plan before starting task execution. The skill requires an upfront critical plan review to surface concerns and questions, preventing wasted effort on unstaged or poorly defined software development tasks.

During the plan review checkpoint, concerns and questions are surfaced to address before any work begins. This critical review prevents wasted effort by ensuring the staged implementation plan is viable before deterministic step execution starts.

Yes, you can hand off completed tasks to a required development-finishing sub-skill. This safe completion workflow ensures tests and options are verified before proceeding, providing a secure handoff after step-by-step plan execution finishes.