mirror of
https://github.com/obra/superpowers.git
synced 2026-08-08 15:22:59 +08:00
Compare commits
3
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
2783fb9145 | ||
|
|
d3f0f13a87 | ||
|
|
96c005307e |
@@ -4,9 +4,10 @@ Superpowers is a complete software development methodology for your coding agent
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [Quickstart](#quickstart)
|
||||
- [How it works](#how-it-works)
|
||||
- [Commercial Services](#commercial-services)
|
||||
- [Getting Started](#installation)
|
||||
- [Installation](#installation)
|
||||
- [Claude Code](#claude-code)
|
||||
- [Antigravity](#antigravity)
|
||||
- [Codex App](#codex-app)
|
||||
@@ -17,10 +18,11 @@ Superpowers is a complete software development methodology for your coding agent
|
||||
- [Gemini CLI](#gemini-cli)
|
||||
- [GitHub Copilot CLI](#github-copilot-cli)
|
||||
- [Grok Build CLI](#grok-build-cli)
|
||||
- [Hermes Agent](#hermes-agent)
|
||||
- [Kimi Code](#kimi-code)
|
||||
- [OpenCode](#opencode)
|
||||
- [Pi](#pi)
|
||||
- [Hermes Agent](#hermes-agent)
|
||||
- [Qwen Code](#qwen-code)
|
||||
- [The Basic Workflow](#the-basic-workflow)
|
||||
- [Community](#community)
|
||||
- [What's Inside](#whats-inside)
|
||||
@@ -30,6 +32,10 @@ Superpowers is a complete software development methodology for your coding agent
|
||||
- [License](#license)
|
||||
- [Visual companion telemetry](#visual-companion-telemetry)
|
||||
|
||||
## Quickstart
|
||||
|
||||
Give your agent Superpowers: [Claude Code](#claude-code), [Antigravity](#antigravity), [Codex App](#codex-app), [Codex CLI](#codex-cli), [Cursor](#cursor), [Devin CLI](#devin-cli), [Factory Droid](#factory-droid), [Gemini CLI](#gemini-cli), [GitHub Copilot CLI](#github-copilot-cli), [Grok Build CLI](#grok-build-cli), [Hermes Agent](#hermes-agent), [Kimi Code](#kimi-code), [OpenCode](#opencode), [Pi](#pi), [Qwen Code](#qwen-code).
|
||||
|
||||
## How it works
|
||||
|
||||
It starts from the moment you fire up your coding agent. As soon as it sees that you're building something, it *doesn't* just jump into trying to write code. Instead, it steps back and asks you what you're really trying to do.
|
||||
@@ -197,6 +203,16 @@ Superpowers is available via the [official Grok plugin marketplace](https://gith
|
||||
/marketplace
|
||||
```
|
||||
|
||||
### Hermes Agent
|
||||
|
||||
Install Superpowers as a Hermes plugin from this repository:
|
||||
|
||||
```bash
|
||||
hermes plugins install obra/superpowers --enable
|
||||
```
|
||||
|
||||
Restart any active Hermes sessions after installing.
|
||||
|
||||
### Kimi Code
|
||||
|
||||
Superpowers is available in Kimi Code's plugin marketplace.
|
||||
@@ -246,17 +262,21 @@ pi -e /path/to/superpowers
|
||||
|
||||
The Pi package loads the Superpowers skills and a small extension that injects the `using-superpowers` bootstrap at session startup and again after compaction. Pi has native skills, so no compatibility `Skill` tool is required. Subagent and task-list tools remain optional Pi companion packages.
|
||||
|
||||
### Hermes Agent
|
||||
### Qwen Code
|
||||
|
||||
Install Superpowers as a Hermes plugin from this repository:
|
||||
Qwen Code installs plugins from Claude Code marketplaces directly.
|
||||
|
||||
- Install the plugin from this repository, and pick `superpowers` when prompted:
|
||||
|
||||
```bash
|
||||
hermes plugins install obra/superpowers --enable
|
||||
qwen extensions install obra/superpowers
|
||||
```
|
||||
|
||||
Restart any active Hermes sessions after installing. Note: Hermes has no
|
||||
post-compaction hook, so a very long session that compacts over its first
|
||||
turn loses the bootstrap — start a fresh session if skills stop triggering.
|
||||
- Update later:
|
||||
|
||||
```bash
|
||||
qwen extensions update superpowers
|
||||
```
|
||||
|
||||
## The Basic Workflow
|
||||
|
||||
|
||||
@@ -182,16 +182,6 @@ Confirm:
|
||||
|
||||
**Other tests fail?** Fix now.
|
||||
|
||||
**"Other tests" means the project's suite, not just your file.** A
|
||||
green run of the test you wrote is not a green suite. Before you call
|
||||
the change done, run the project's test command (bare `pytest`,
|
||||
`npm test`, `cargo test` — whatever the repo uses) even when your task
|
||||
named only one test file. A scope statement in your task bounds the
|
||||
deliverable, not your verification. Any failure that run shows —
|
||||
including one you didn't cause — goes in your report by name; a red
|
||||
test you watched scroll past and didn't mention is a report falsified
|
||||
by omission.
|
||||
|
||||
### REFACTOR - Clean Up
|
||||
|
||||
After green only:
|
||||
|
||||
Reference in New Issue
Block a user