ワンクリックで
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | executing-plans |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
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 Codex 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:
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
将任务派发给后台 agent 执行。用法:/dispatch "任务描述"
Review and summarize the current conversation session. Use this skill whenever the user says 'review', 'summarize session', 'session summary', 'wrap up', 'what did we do', 'checklist', or any variation of wanting to look back at what happened in the conversation. Also triggers on Chinese equivalents like '复盘', '总结', '回顾对话', '收尾'. Always use this skill at the end of a working session, even if the user just says 'done' or 'finished' — offer to run a review.
查看后台任务状态。用法:/task-status 或 /task-status <id>
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment