Skill Detail

Install Superpowers methodology for coding agents

Use Superpowers to give coding agents a structured software-development method with discovery, spec review, planning, TDD, subagents, and review loops.

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Security Reviewed
⭐ 194.6k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill install-superpowers-methodology-for-coding-agents Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Supported coding-agent harness such as Claude Code, Codex, Cursor, Gemini CLI, OpenCode, or Factory Droid
Install & setup
Install Superpowers through the supported plugin or marketplace path for the target agent harness, then start a coding task and let the agent follow the Superpowers workflow.
Author
Jesse Vincent
Publisher
Individual
Last updated
May 17, 2026
Quick brief

Use Superpowers to add a practical development methodology to coding agents across Claude Code, Codex, Cursor, Gemini CLI, OpenCode, and related harnesses. The operator installs the matching plugin or skill bundle, then lets the agent follow the Superpowers flow: clarify the goal, produce a spec, get approval, plan implementation, use TDD where appropriate, delegate subtasks, and review the result.

How it works

What this skill actually does

Invoke this when a coding agent needs disciplined project execution rather than an unstructured coding prompt. The boundary is the repeatable agentic software-development process and skill set, not a generic plugin marketplace listing or a single IDE feature.

Inputs and prerequisites: Supported coding-agent harness such as Claude Code, Codex, Cursor, Gemini CLI, OpenCode, or Factory Droid.

Setup notes: Install Superpowers through the supported plugin or marketplace path for the target agent harness, then start a coding task and let the agent follow the Superpowers workflow.

Source and verification boundary: use https://github.com/obra/superpowers as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.