| name | m-executing-plans |
| description | Executes a written implementation plan inline, task by task, following each step exactly and stopping at blockers. Use when a plan exists and subagent dispatch is unavailable or unwanted; otherwise prefer m-subagent-driven-development. Triggers: execute the plan, run the plan, implement the plan. |
Executing Plans
Overview
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the m-executing-plans skill to implement this plan."
Note: If subagents are available on this platform, use m-subagent-driven-development instead of this skill.
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with the user before starting
- If no concerns: Create a task list in your todo-tracking tool and proceed
Step 2: Execute Tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Step 3: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the m-finishing-a-development-branch skill to complete this work."
- REQUIRED SUB-SKILL: Use m-finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- You don't understand an instruction
- Verification fails repeatedly
Ask for clarification rather than guessing.
When to Revisit Earlier Steps
Return to Review (Step 1) when:
- The user updates the plan based on your feedback
- Fundamental approach needs rethinking
Don't force through blockers - stop and ask.
Remember
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Reference skills when plan says to
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent
Integration
Required workflow skills:
- m-using-git-worktrees - Ensures isolated workspace (creates one or verifies existing)
- m-writing-plans - Creates the plan this skill executes
- m-finishing-a-development-branch - Complete development after all tasks
