Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows superpowers OpenClaw

Superpowers

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.

740 installs · 25 stars

Official URL:ClawHub

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Spec-first, TDD, subagent-driven software development workflow

When to use it

(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

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Superpowers — OpenClaw Edition; The Pipeline; Phase 1: Brainstorming; Phase 2: Writing Plans; Phase 3: Subagent-Driven Development; Phase 4: Systematic Debugging.

File analysis

File analysis: besides SKILL.md, the body references references/brainstorming.md, references/writing-plans.md, references/subagent-development.md, references/tdd.md, references/systematic-debugging.md, references/finishing-branch.md. Those resources load on demand.

Superpowers — OpenClaw EditionThe PipelinePhase 1: BrainstormingPhase 2: Writing PlansPhase 3: Subagent-Driven DevelopmentPhase 4: Systematic DebuggingPhase 5: Finishing a BranchOpenClaw Subagent Dispatch PatternKey Principles

Source category:ClawHub Debugging

SKILL.md & Agent activation

Official spec ↗
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.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 6
  • references/brainstorming.md
  • references/writing-plans.md
  • references/subagent-development.md
  • references/tdd.md
  • references/systematic-debugging.md
  • references/finishing-branch.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "superpowers" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-2480c0081c6b021c-Superpowers.html
Save it as .cursor/skills/superpowers/SKILL.md or .claude/skills/superpowers/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://clawhub.ai/skills/superpowers instead of creating only a SKILL.md.

No unambiguous GitHub package URL is recorded. Follow the original source's installer instructions.

ClawHub ↗

Readable layout
--- 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--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-.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

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Find Skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can…