# Superpowers

Use composable development skills when repeatable design, testing, debugging, and review steps are the priority.

ID: superpowers
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/superpowers/

## Why: the goal or problem

A recipe app lets cooks scale ingredient quantities. Halving servings produces the wrong flour amount. Its developer needs a repeatable test-and-review repair process; preserving a product specification alone does not establish that habit.

## How: work toward a solution

Agree on the scaling rule, write a test for 200 g becoming 100 g, observe failure, fix the calculation, and rerun checks. Review the change against the agreed plan.

## What: the concept

Superpowers packages development workflows as composable agent skills. Installation and activation depend on the harness. Its procedures add work; prefer existing checks when sufficient, and a specification workflow when durable requirement tracking is the priority.

[Source](https://github.com/obra/superpowers)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

The priority here is a repeatable development procedure: clarify design, plan work, verify a regression, and review the result. Superpowers includes skills for those activities. Spec Kit or OpenSpec can hold durable requirements if needed; identify which records and approvals govern execution before combining them. Existing project instructions and an ordinary agent may already provide enough discipline. These selection criteria are editorial judgments, not measured quality rankings.

## Applications

The fictional recipe uses 200 g of flour for four servings. Two servings require 100 g; an illustrated failing result of 200 g exposes the bug. A meaningful test exercises the scaling behavior, then the developer observes it fail before changing code and pass afterward. Review includes other agreed quantities and rounding rules where relevant. The diagram illustrates this process and does not execute tests or demonstrate an actual model result.

## Implementation & cautions

Read the current official installation instructions for the external agent in use. The project documents plugin or extension installation by harness; Codex CLI currently exposes a plugin selection flow. If the assistant cannot operate that flow, provide the exact user step and retain the setup status as pending. Inspect the installed skills, hooks, scope, and active version before use. Invoke or load the needed skill and confirm its output; installation alone does not establish activation. Reuse approved requirements and preserve project-specific test and delegation limits. Do not treat subagent, worktree, merge, or publish instructions as extra authorization. A full workflow can impose more ceremony than a small correction needs.

## Evidence

- [Superpowers README](https://github.com/obra/superpowers) — Superpowers combines composable development skills and documents harness-specific plugin and extension setup. (Checked: 2026-10-08)
- [Superpowers test-driven development skill](https://github.com/obra/superpowers/blob/main/skills/test-driven-development/SKILL.md) — The test-first workflow checks failure before a minimal implementation and then checks passing behavior. (Checked: 2026-10-08)
- [Superpowers brainstorming skill](https://github.com/obra/superpowers/blob/main/skills/brainstorming/SKILL.md) — Design clarification reuses supplied context and requires the selected path’s design prerequisites before implementation. (Checked: 2026-10-08)