Menu
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants a plan or design stress-tested before implementation, or asks to be grilled, interviewed, or interrogated about a decision tree.
Disciplined root-cause investigation for hard bugs and performance regressions, with findings pinned to the case board. Use when user reports a bug, says something is broken/throwing/failing, describes a performance regression, or asks to diagnose/debug/investigate something.
Use when writing a commit message — "write a commit", "commit message", "generate commit", "/commit", or invokes /faceless-commit, or when staging changes. Legacy alias: "/caveman-commit".
Use when reviewing code or a diff — "review this PR", "code review", "review the diff", "/review", or invokes /faceless-review. Legacy alias: "/caveman-review".
Use when the user wants terse, compressed, low-token responses — "faceless mode", "talk faceless", "be brief", "less tokens", "compress", or invokes /faceless. Also when token efficiency is explicitly requested. Legacy aliases: "caveman mode", "use caveman".
Use when turning raw material — research, notes, interview answers, fragments, or investigation findings — into a sourced written report or article, or when shaping, drafting, restructuring, or tightening such a draft. Triggers: "write up the findings", "investigative report", "turn these notes into an article", "draft the report", "shape this into an article", "edit the article", "help me write this up".
| name | executing-plans |
| version | 2.0 |
| category | superpowers |
| execution_speed | medium |
| token_efficiency | medium |
| triggers | ["execute plan","written plan","implementation plan","follow steps"] |
| cache_key | executing-plans-2.0 |
| dependencies | [] |
| disable-model-invocation | true |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
Follow the global Long-Workflow Resilience rule (CLAUDE.md): the plan's task list is the checkpoint -- keep TodoWrite current as each task completes. On an API error (500, 529 overload, usage limit), stop cleanly and name the next incomplete task to resume from; do not redo committed tasks.
Single-agent sequential execution. For parallel execution across multiple agents, use /subagent-driven-development.
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Note: Tell your human partner that Superpowers works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
For each task:
After all tasks complete and verified:
STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
Required workflow skills:
