executing-plans

Executing a development plan step by step involves loading the plan, questioning risks, confirming with stakeholders, and tracking per-task state transitions with embedded verifications. This workflow automates task execution sequentially while enforcing human approval at critical review checkpoints before proceeding.

Tracking task execution status and identifying blockers requires explicit per-task state transitions paired with continuous verification checks. The process surfaces blockers during the initial plan review and monitors progress throughout execution, ensuring development work remains unobstructed and transparently reported.

Automating plan execution while requiring human confirmation is supported by loading the plan, critically reviewing it to surface concerns, and pausing for explicit approval. Once confirmed, the workflow executes tasks sequentially with embedded verifications, balancing automated processing with controlled human oversight.

Finalizing a development workflow after completing planned tasks involves transitioning to a designated finishing sub-skill and generating a final completion report. This end-to-end workflow ensures all verifications pass and task states are complete before closing the project work session with documented results.

Git-worktrees integration is supported within the plan execution workflow, allowing isolated development environments for task-by-task implementation. The workflow applies verifications and state transitions within these worktrees to maintain clean boundaries and prevent missteps during controlled project work sessions.

If an implementation plan has unresolved risks or missing verification steps, the execution workflow pauses during the initial critical review phase to surface questions and concerns. It requires obtaining human confirmation and addressing blockers before proceeding, preventing missteps and miscommunication later in task execution.