superpowers-executing-plans
Use when executing a written implementation plan in the current session with sequential task execution and review checkpoints - for when subagent-driven mode is not available
Best use case
superpowers-executing-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when executing a written implementation plan in the current session with sequential task execution and review checkpoints - for when subagent-driven mode is not available
Teams using superpowers-executing-plans should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openclaw-executing-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How superpowers-executing-plans Compares
| Feature / Agent | superpowers-executing-plans | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when executing a written implementation plan in the current session with sequential task execution and review checkpoints - for when subagent-driven mode is not available
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Superpowers Executing Plans（OpenClaw 顺序执行版） ## 概述 加载计划，批判性审查，按顺序执行所有任务，有审查检查点。 **开始时宣布：** "我正在用 executing-plans 技能实现这个计划。" **注意：** Superpowers 在有 subagent 支持的平台（Claude Code、Codex）工作质量高得多。如果 subagent 可用，用 `superpowers-subagent-dev` 而不是这个技能。 ## OpenClaw 适配 OpenClaw 的 `sessions_spawn` 支持 subagent，可以用 `superpowers-subagent-dev` 获得更好质量。这个技能用于： - subagent 不可用的环境 - 简单任务不需要 subagent 开销 - 学习和测试计划质量 ## 流程 ### 步骤 1：加载和审查计划 1. 读计划文件 2. 批判性审查——识别任何问题或顾虑 3. 如果有顾虑：开始前向主人提出 4. 如果无顾虑：创建任务列表并继续 ### 步骤 2：执行任务 每个任务： 1. 标记为进行中 2. 按计划精确执行每步（计划有小的粒度步骤） 3. 按指定运行验证 4. 标记为完成 ### 步骤 3：完成开发 所有任务完成并验证后： - 宣布："我正在用 finishing-a-development-branch 技能完成这项工作。" - 使用 `superpowers-finishing-branch` 技能 - 按该技能验证测试、展示选项、执行选择 ## 何时停止并求助 **立即停止执行当：** - 遇到阻塞（缺失依赖、测试失败、指令不清） - 计划有阻止开始的重大缺口 - 不理解某个指令 - 验证反复失败 **宁可提问，不要猜测。** ## 何时回顾早期步骤 **回到审查（步骤 1）当：** - 主人根据反馈更新了计划 - 基本方法需要重新思考 **不要强行突破阻塞** — 停止并提问。 ## 批次执行（推荐） 对于长计划，按批次执行： ``` 每完成 3 个任务： → 运行审查（请求 code review） → 获得反馈，应用，继续 ``` 批次审查防止问题级联。 ## 计划质量信号 如果计划质量差（步骤模糊、缺少验证、占位符多）： - 在开始前指出问题 - 与主人讨论解决方案 - 不要强行按坏计划执行 ## 记住 - 先批判性审查计划 - 精确按计划步骤执行 - 不要跳过验证 - 引用计划说到的技能 - 阻塞时停止，不要猜 - 未获主人明确同意不要在 main/master 分支上开始实现 ## 集成 **必需的工作流技能：** - `superpowers-isolated-workspace` — 开始前 REQUIRED：建立隔离工作区 - `superpowers-writing-plans` — 创建这个技能执行的计划 - `superpowers-finishing-branch` — 所有任务完成后的收尾 - `superpowers-verification` — 每个步骤验证 - `superpowers-tdd` — 每个任务遵循 TDD
Related Skills
superpowers-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code - guides writing comprehensive implementation plans with bite-sized tasks, TDD, and DRY/YAGNI principles
superpowers-verification
Use when about to claim any work is complete, fixed, passing, or successful - requires running fresh verification commands and reading actual output before making any success claims; evidence before assertions always
superpowers-tdd
Use when implementing any feature or bugfix, before writing implementation code - enforces RED-GREEN-REFACTOR cycle: write failing test first, verify it fails, write minimal code, verify it passes, then refactor
superpowers-systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior - enforces systematic four-phase debugging: root cause investigation, pattern analysis, hypothesis testing, and evidence-based fix verification
superpowers-subagent-dev
Use when executing implementation plans with independent tasks - coordinates task execution by dispatching subagents per task with verification checkpoints, adapted for OpenClaw's isolated session model
superpowers-parallel-agents
Use when facing 2 or more independent tasks that can be worked on without shared state - dispatches parallel subagents using sessions_spawn for concurrent investigation and execution, adapted for OpenClaw
superpowers-overview
Use when starting any development work or when unsure which superpowers development skill to use - provides entry point and navigation to the full superpowers skill suite for OpenClaw agents
superpowers-isolated-workspace
Use when starting feature work that needs isolation from current workspace - creates isolated git branches with clean setup and safety verification, adapted for OpenClaw environments
superpowers-finishing-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - presents structured options for merge, PR, or cleanup; adapted for OpenClaw git workflow without worktrees
superpowers-brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior - guides through exploration, questioning, design proposal, and spec documentation before any implementation
superpowers-requesting-code-review
Use when completing tasks, implementing major features, or before merging - dispatches code review subagent to catch issues before they cascade, adapted for OpenClaw sessions_spawn model
superpowers-receiving-code-review
Use when receiving code review feedback - requires technical verification before implementing suggestions, with reasoned pushback when feedback is technically questionable; no performative agreement