How do I install the Superpowers Mode skill?

Run npx skillmds@latest add modbender/superpowers-mode in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Superpowers Mode safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Superpowers Mode?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Superpowers Mode free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Superpowers Mode?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Superpowers Mode by modbender — Agent Skill

Name: Superpowers Mode
Rating: 4.2 (5 reviews)
Author: modbender

Superpowers Mode

Enable or disable a strict engineering workflow inspired by obra/superpowers when the user explicitly asks (e.g., "включи superpowers", "disable superpowers"). When enabled and the task is coding/build/debug, enforce: clarify goal, write spec, write plan, execute in small steps (prefer TDD), then review/finish. Use this skill only for coding workflows, not general chat.

modbender Updated Sep 9, 2026 12 repo stars

File contents

Superpowers Mode (On-demand)

Use this only when the user explicitly asks to enable/disable this mode, or when mode is already enabled for coding tasks.

State file

Track mode in:

memory/superpowers-mode.md

Format:

enabled: true|false
updatedAt: <ISO>
notes: <optional>

Commands

Enable phrases: включи superpowers, enable superpowers, superpowers on
- Write enabled: true to the state file.
- Confirm in 1 short message.
Disable phrases: выключи superpowers, disable superpowers, superpowers off
- Write enabled: false.
- Confirm in 1 short message.
Status phrases: статус superpowers, superpowers status
- Read state and report enabled/disabled.

Workflow when enabled (coding tasks only)

For coding/build/debug requests, follow this order:

Clarify objective and constraints quickly.
Produce a short spec (chunked, easy to review).
Produce an implementation plan with small tasks.
(Optional, 30 sec) Run a mini risk review:
- How can this fail in production?
- What is the weakest dependency/state assumption?
- What signal will show regression + how to rollback fast?
Execute task-by-task (prefer test-first for risky changes).
Verify against acceptance criteria, then summarize outcome + next step.

Use templates from references/ when useful.

Red flags (quick self-check)

If you notice these thoughts, slow down and apply the workflow:

"Сейчас быстро вкачу без плана" for non-trivial changes.
"И так понятно, тесты потом" on risky edits.
"Откат не нужен" before touching config/auth/cron/system files.
"Похоже работает" without explicit verification.

Guardrails

Do not force this workflow for non-coding chat.
If user asks for speed (quick, без плана, just do it), skip to minimal plan and execute.
Keep updates concise; avoid process spam.

---name: superpowers-modedescription: Enable or disable a strict engineering workflow inspired by obra/superpowers when the user explicitly asks (e.g., "включи superpowers", "disable superpowers"). When enabled and the task is coding/build/debug, enforce: clarify goal, write spec, write plan, execute in small steps (prefer TDD), then review/finish. Use this skill only for coding workflows, not general chat.--- # Superpowers Mode (On-demand) Use this only when the user explicitly asks to enable/disable this mode, or when mode is already enabled for coding tasks. ## State file Track mode in: `memory/superpowers-mode.md` Format: ```md enabled: true|false updatedAt: <ISO> notes: <optional> ``` ## Commands - Enable phrases: `включи superpowers`, `enable superpowers`, `superpowers on` - Write `enabled: true` to the state file. - Confirm in 1 short message. - Disable phrases: `выключи superpowers`, `disable superpowers`, `superpowers off` - Write `enabled: false`. - Confirm in 1 short message. - Status phrases: `статус superpowers`, `superpowers status` - Read state and report enabled/disabled. ## Workflow when enabled (coding tasks only) For coding/build/debug requests, follow this order: 1. Clarify objective and constraints quickly. 2. Produce a short spec (chunked, easy to review). 3. Produce an implementation plan with small tasks. 4. (Optional, 30 sec) Run a mini risk review: - How can this fail in production? - What is the weakest dependency/state assumption? - What signal will show regression + how to rollback fast? 5. Execute task-by-task (prefer test-first for risky changes). 6. Verify against acceptance criteria, then summarize outcome + next step. Use templates from `references/` when useful. ## Red flags (quick self-check) If you notice these thoughts, slow down and apply the workflow: - "Сейчас быстро вкачу без плана" for non-trivial changes. - "И так понятно, тесты потом" on risky edits. - "Откат не нужен" before touching config/auth/cron/system files. - "Похоже работает" without explicit verification. ## Guardrails - Do not force this workflow for non-coding chat. - If user asks for speed (`quick`, `без плана`, `just do it`), skip to minimal plan and execute. - Keep updates concise; avoid process spam.

Frequently asked questions