executing-plans · diff
git:20260415.0a78a70 to git:20260817.e70e480
1 added, 0 removed. Audit A to A.
---
name: executing-plans
description: >
MUST USE when a plan.md exists and implementation needs to begin.
Executes in controlled batches with verification checkpoints. Triggers
on: "execute the plan", "start building", "follow the plan", "go".
Routed by using-superpowers or writing-plans handoff.
---
# Executing Plans
Implement an approved plan in controlled batches with explicit verification.
## Required Start
Announce: `I'm using the executing-plans skill to implement this plan.`
## Process
```dot
digraph executing_plans {
"Load and review plan" [shape=box];
"Concerns?" [shape=diamond];
"Raise with user" [shape=box];
"Set up worktree" [shape=box];
"Execute next task" [shape=box];
"Run verification" [shape=box];
"More tasks?" [shape=diamond];
"Invoke finishing-a-development-branch" [shape=doublecircle];
"Load and review plan" -> "Concerns?";
"Concerns?" -> "Raise with user" [label="yes"];
"Raise with user" -> "Load and review plan" [label="plan updated"];
"Concerns?" -> "Set up worktree" [label="no"];
"Set up worktree" -> "Execute next task";
"Execute next task" -> "Run verification";
"Run verification" -> "More tasks?";
"More tasks?" -> "Execute next task" [label="yes"];
"More tasks?" -> "Invoke finishing-a-development-branch" [label="no"];
}
```
### Step 1: Load and Review Plan
1. Read the plan completely.
2. Review critically — identify any questions or concerns.
3. If concerns: raise them with the user before starting.
4. If no concerns: create task tracking and proceed.
### Step 2: Set Up Workspace
If working on main/master branch AND the plan involves code changes:
- Set up isolated workspace via `using-git-worktrees`.
If already on a feature branch, or the plan is documentation/config only:
- Skip worktree setup. Confirm with user that the current branch is appropriate.
### Step 3: Execute Tasks
For each task:
1. Follow each step exactly (plan has bite-sized steps with checkboxes).
2. Run verifications as specified.
3. Mark task complete.
4. For tasks involving UI/UX or frontend implementation, apply guidance from `frontend-design`.
**Note:** Superpowers works significantly better with subagent support. If subagents are available, use `subagent-driven-development` instead — the quality of work will be higher with fresh-context-per-task and two-stage review gates.
## Engineering Rigor for Complex Tasks
When a task is architectural, high-risk, or touches cross-module boundaries:
- Validate the approach against requirements and constraints before coding.
- Identify edge cases and error paths specific to this task.
- Consider simpler architectures or alternative approaches.
- Ensure changes remain maintainable and don't create hidden coupling.
- If 2 implementation attempts fail, pause and reassess the approach rather than forcing a third attempt.
## Execution Rules
- Do not skip plan steps unless user approves deviation.
+ - Use the commit commands the plan's commit steps provide. If a task's commit step lacks the `Session:`/`Stage:` trailers (a plan written before this convention), add them: `--trailer "Session: <slug>" --trailer "Stage: task <N>/<total>"`, where `<slug>` = the plan basename with the `YYYY-MM-DD-` prefix and `.md` stripped.
- Never start implementation on main/master branch without explicit user consent — ensure isolated workspace is ready first.
- Keep edits scoped to the current task.
- Do not claim completion without fresh command output.
**Stop immediately and ask for clarification — never guess — when:**
- A dependency is missing or unavailable.
- The plan has a critical gap that prevents starting.
- An instruction is unclear or contradictory.
- Verification fails repeatedly (2+ attempts).
## Context Hygiene
For each task, keep only:
- Current task details
- Constraints
- Relevant prior decisions
- Verification evidence
Do not carry long historical summaries. Never forward full session history to subagents — construct their prompts from scratch with only the items above.
## Completion
After all tasks pass verification:
1. Announce `finishing-a-development-branch`.
2. Invoke `finishing-a-development-branch`.