According to AlphaMoat, as of 2026-10, Superpowers Dev Workflow has 37,274 downloads and 38 stars — ranked by downloads #701 among 10,914 AI skills in this ranking, and #46 of 1,069 in Development.
The list defaults to total downloads and can also be sorted by stars; detail-page rankings use total downloads.
| Platform | Downloads | Stars | Comments |
|---|---|---|---|
| ClawHub ↗ | 30.7K | 24 | - |
| SkillHub ↗ | 37.3K | 38 | — |
Platforms count differently and update at different times.
It explores project context first, then asks clarifying questions one at a time, proposes two or three approaches with trade-offs, and writes no code until the user approves the design. During implementation a subagent reviews code against the spec. The workflow is mandatory, not advisory. The workflow requires exec and sessions_spawn tools for its specified subprocess review. If unavailable, do not claim that a subagent review occurred.
Profile published 2026-10-27
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change. Other skills share this name; figures from before the change are attributed to this one, which currently has the most downloads.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-10 | 37.3K | — | 38 |
| 2026-09 | 28.5K | — | 38 |
| 2026-08 | 26.8K | +11.8% | 37 |
| 2026-07 | 24.0K | +15.9% | 35 |
| 2026-06 | 20.7K | +12.8% | 30 |
| 2026-05 | 18.3K | — | 23 |
| 2026-03 | 9.3K | — | 6 |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.
--- name: superpowers description: > Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan → subagent execution loop, (2) debugging a bug or test failure — triggers systematic root-cause process, (3) user says "let's build", "help me plan", "I want to add X", or "this is broken", (4) completing a feature branch — triggers test verification + merge/PR options. NOT for: one-liner fixes (just edit), reading code, or non-code tasks. Requires exec tool and sessions_spawn.
--- # Superpowers — OpenClaw Edition Adapted from [obra/superpowers](https://github.com/obra/superpowers). Mandatory workflow — not suggestions. ## The Pipeline ``` Idea → Brainstorm → Plan → Subagent-Driven Build (TDD) → Code Review → Finish Branch ``` Every coding task follows this pipeline. "Too simple to need a design" is always wrong. --- ## Phase 1: Brainstorming **Trigger:** User wants to build something. Activate before touching any code. **See:** [references/brainstorming.md](references/brainstorming.md) **Summary:** 1. Explore project context (files, docs, recent commits) 2. Ask clarifying questions — **one at a time**, prefer multiple choice 3. Propose 2–3 approaches with trade-offs + recommendation 4. Present design in sections, get approval after each 5. Write design doc → `docs/plans/YYYY-MM-DD-<topic>-design.md` → commit 6. Hand off to **Phase 2: Writing Plans** **HARD GATE:** Do NOT write any code until user approves design. --- ## Phase 2: Writing Plans **Trigger:** Design approved. Activated by brainstorming phase. **See:** [references/writing-plans.md](references/writing-plans.md) **Summary:** - Write a detailed task-by-task implementation plan - Each task = 2–5 minutes: write test → watch fail → implement → watch pass → commit - Save to `docs/plans/YYYY-MM-DD-<feature>.md` - Announce: `"I'm using the writing-plans skill to create the implementation plan."` - After saving, offer two execution modes: - **Subagent-driven (current session):** `sessions_spawn` per task + two-stage review - **Manual execution:** User runs tasks themselves --- ## Phase 3: Subagent-Driven Development **Trigger:** Plan exists, user chooses subagent-driven execution. **See:** [references/subagent-development.md](references/subagent-development.md) **Per-task loop (OpenClaw):** 1. `sessions_spawn` an implementer subagent with task + full plan context 2. Wait for completion announcement 3. `sessions_spawn` a spec-reviewer subagent → must confirm code matches spec 4. `sessions_spawn` a code-quality reviewer subagent → must approve quality 5. Fix any issues, re-review if needed 6. Mark task done, move to next 7. Final: dispatch overall code reviewer → hand off to Phase 5 **TDD is mandatory in every task.** See [references/tdd.md](references/tdd.md). --- ## Phase 4: Systematic Debugging **Trigger:** Bug, test failure, unexpected behaviour — any technical issue. **See:** [references/systematic-debugging.md](references/systematic-debugging.md) **HARD GATE:** No fixes without root cause investigation first. **Four phases:** 1. Root Cause Investigation (read errors, reproduce, check recent changes, trace data flow) 2. Pattern Analysis (find working examples, compare, identify differences) 3. Hypothesis + Testing (one hypothesis at a time, test to prove/disprove) 4. Fix + Verification (fix at root, not symptom; verify fix doesn't break anything) --- ## Phase 5: Finishing a Branch **Trigger:** All tasks complete, all tests pass. **See:** [references/finishing-branch.md](references/finishing-branch.md) **Summary:** 1. Verify all tests pass 2. Determine base branch 3. Present 4 options: merge locally / push + PR / keep / discard 4. Execute choice 5. Clean up --- ## OpenClaw Subagent Dispatch Pattern When dispatching implementer or reviewer subagents, use `sessions_spawn`: ``` Goal: [one sentence] Context: [why it matters, which plan file] Files: [exact paths] Constraints: [what NOT to do — no scope creep, TDD only] Verify: [how to confirm success — tests pass, specific command] Task text: [paste full task from plan] ``` Run `sessions_spawn` with the task as a detailed prompt. The sub-agent announces results automatically. --- ## Key Principles - **One question at a time** during brainstorm - **TDD always** — write failing test first, delete code written before tests - **YAGNI** — remove unnecessary features from all designs - **DRY** — no duplication - **Systematic over ad-hoc** — follow the process especially under time pressure - **Evidence over claims** — verify before declaring success - **Frequent commits** — after each green test
【全栈能力】编程大神.Skill:面向复杂真实项目的高阶全栈编程助手。不止生成代码,而是从一句目标接手陌生代码库,拆解需求、补齐实现、追到根因、完成重构、联调前后端,并把结果推进到能运行、能验证、能交付。覆盖 Web、后端、脚本、iOS、安卓、鸿蒙 ArkUI、微信小程序及其他技术栈,支持中英文工程、疑难 Bug、跨模块任务和长任务续做;用构建、日志、真实入口、设备或接口证据说明结果。仅问概念时直接回答,要求落地时持续推进到验收或明确阻塞。
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
工程专题、鸿蒙与微信小程序开发的集成派生版
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
适用场景:全栈编程助手。接到需求先读现有代码和约束,再动手:Java/PHP 开发、接口设计、缺陷定位、代码评审、重构、测试用例、性能排查、技术选型与文档产出,也做 CMS 二次开发、前端页面和 MySQL 调优。每次改动先给方案和影响范围,改完必须跑验证,交付附交接说明。适合要把代码真正跑通、而不是只要片段的场景。写完代码常要配套的造价、法律、工程文档,站内已有现成技能,用「查找技能」按需求找即可。
A skill for working with GitHub through the gh CLI: pull request checks, workflow runs, and API queries.
Data as of 2026-10. Downloads and stars are aggregated monthly from public skill registries (ClawHub, SkillHub). See data methodology.