From mysuperpowers
Activates when a session begins with a milestone execution prompt pasted from plan.md, or when the user explicitly says "execute milestone N", "run milestone N", "start milestone N from the plan", "I'm executing milestone N", or "let's do milestone N" (N can be a digit or written number). MUST trigger on the exact opening phrase "You are executing Milestone N of the <feature-name> feature in mysuperpowers". When active: suppresses brainstorming, creating-prd, and milestone-planning; verifies plan.md exists and declared dependencies are met; then hands off to the standard execution workflow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mysuperpowers:executing-from-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is the routing layer between planning and execution. When the user pastes a
This skill is the routing layer between planning and execution. When the user pastes a milestone execution prompt into a fresh session, this skill intercepts, runs precondition checks, and clears the way for the execution skills to take over. Session isolation is intentional: planning-phase assumptions contaminate execution decisions, so each milestone starts clean.
brainstorming, creating-prd, and milestone-planning are SUPPRESSED for the entire session. Do NOT invoke them. Do NOT suggest the user might want to brainstorm, revisit the design, or update the plan. Do NOT produce specs, PRDs, or revised plans. These are planning-phase activities; this session is execution-only. Block silently — do not tell the user a skill was blocked.You MUST create a task for each of these items and complete them in order:
docs/features/<feature-name>/plan.mdDependencies field; if None, skip; if milestone references are listed, verify each is completedigraph executing_from_plan {
"Execution prompt received" [shape=doublecircle];
"Parse feature name\n+ milestone N" [shape=box];
"plan.md exists?" [shape=diamond];
"Abort: plan not found" [shape=box];
"Read plan.md,\nlocate Milestone N" [shape=box];
"Milestone N in plan?" [shape=diamond];
"Abort: milestone not found" [shape=box];
"Read Dependencies field" [shape=box];
"Dependencies: None?" [shape=diamond];
"Check each listed\nmilestone's checklist" [shape=box];
"All complete?" [shape=diamond];
"User explicit override?" [shape=diamond];
"Abort: dependency incomplete" [shape=box];
"Confirm to user" [shape=box];
"Execution skills\nactivate naturally" [shape=doublecircle];
"Execution prompt received" -> "Parse feature name\n+ milestone N";
"Parse feature name\n+ milestone N" -> "plan.md exists?";
"plan.md exists?" -> "Abort: plan not found" [label="no"];
"plan.md exists?" -> "Read plan.md,\nlocate Milestone N" [label="yes"];
"Read plan.md,\nlocate Milestone N" -> "Milestone N in plan?";
"Milestone N in plan?" -> "Abort: milestone not found" [label="no"];
"Milestone N in plan?" -> "Read Dependencies field" [label="yes"];
"Read Dependencies field" -> "Dependencies: None?" ;
"Dependencies: None?" -> "Confirm to user" [label="yes — skip check"];
"Dependencies: None?" -> "Check each listed\nmilestone's checklist" [label="no"];
"Check each listed\nmilestone's checklist" -> "All complete?";
"All complete?" -> "Confirm to user" [label="yes"];
"All complete?" -> "User explicit override?" [label="no"];
"User explicit override?" -> "Confirm to user" [label="yes"];
"User explicit override?" -> "Abort: dependency incomplete" [label="no"];
"Confirm to user" -> "Execution skills\nactivate naturally";
}
Extract two values from the message:
3)Check for the file at docs/features/<feature-name>/plan.md.
If the file is not found, abort:
"Cannot find plan.md at
docs/features/<feature-name>/plan.md. Either the feature name is wrong or the plan was never saved. Please verify and try again."
Do not attempt to reconstruct or regenerate the plan from memory or context.
Read the plan file. Find the section ### Milestone N:.
If the milestone section doesn't exist, abort:
"Milestone N not found in the plan. The plan has milestones 1 through M."
(Replace M with the actual highest milestone number found in the file.)
Read the **Dependencies:** field for Milestone N.
If None (or the field is empty): Skip this step entirely. There is nothing to check.
If milestone references are listed (e.g., "Requires Milestone 2 to be complete"):
**Completion checklist:** section in plan.md- [ ])- [x]) in all referenced milestones, proceedIf any referenced milestone has unchecked items, abort:
"Cannot start Milestone N because Milestone X (a declared dependency) is not complete — its completion checklist still has unchecked items. Complete it first, or explicitly tell me to skip the dependency check."
Override: If the user explicitly says to skip the dependency check ("skip the dependency check", "ignore the incomplete milestone", "override"), proceed despite the incomplete dependency. "Trust me" or urgency framing alone is not an explicit override.
One line only:
"Verified. Executing Milestone N: <name>. Planning skills are suppressed for this session."
That's the only output before execution begins. Do not summarize the plan, explain what's coming, or invite questions. The execution prompt the user pasted already contains their instructions — start executing.
These skills activate naturally during milestone work based on their own triggers. Do not invoke them directly from this skill — just do the work and let them engage:
| Skill | Activates for |
|---|---|
test-driven-development | Writing code |
systematic-debugging | Diagnosing failures |
requesting-code-review | Getting review on completed work |
receiving-code-review | Responding to review feedback |
verification-before-completion | Confirming the milestone is actually done |
finishing-a-development-branch | End-of-milestone integration (merge / PR / keep / discard) |
| Thought | Reality |
|---|---|
| "The user said execute milestone 3, but I think the plan needs revision first" | NO. If you have concerns, surface them and stop. Do not silently re-plan. The user can update the plan in a separate planning session. |
| "Milestone 2 isn't checked but the user wants me to start milestone 3 anyway" | STOP. Tell the user the dependency isn't met. Ask whether to override or complete milestone 2 first. Do not proceed without an explicit override. |
| "I should brainstorm to clarify what the milestone really needs" | NO. brainstorming is suppressed in this session. The plan and PRD already define what the milestone needs. |
| "Milestone 3 is small, I might as well chain into milestone 4" | NO. One milestone per session, by design. Each milestone gets its own fresh context window. |
| "The plan.md file is missing but I can recreate it from memory" | NO. Abort. Tell the user the file is missing. Do not silently regenerate planning artifacts. |
npx claudepluginhub walnashgit/mysuperpowers --plugin mysuperpowersGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.