executing-plans

Executing a development plan involves loading a pre-written implementation plan, enforcing critical review checkpoints, and performing step-by-step verifications after each task. This skill coordinates structured task execution and completion reporting across isolated work sessions.

Automating workflow execution across isolated sessions requires a deterministic workflow that loads the plan, executes tasks with status updates, and enforces stop conditions. This skill coordinates staged execution and completion reporting while handling blockers.

Yes, you can use this plan execution workflow with blocked tasks. The skill handles blockers during task execution, allowing you to stop or revisit steps as needed before proceeding to the next verification checkpoint or subskill integration.

Yes, you need a pre-written implementation plan before starting task execution. This skill applies to scenarios where a plan already exists and requires staged execution, verification, and completion reporting rather than generating the plan itself.

Plan execution supports integration with subagents and additional tools for higher quality outcomes. It aligns with required workflow skills like using git worktrees and finishing a development branch to manage isolated work sessions.