Slow-powers gives your agent superpowers. It's a complete software development methodology for coding agents — a set of composable skills plus a bootstrap that ensures the agent reaches for them at the right moments.
Slow-powers is a fork of obra/superpowers at v5.1.0. We preserve the overall workflow of superpowers, while fixing bugs and clarifying skill content.
Give your agent superpowers with slow-powers: Claude Code · Codex CLI · OpenCode. Support varies per harness — see the feature support table.
| Harness | Status | Notes |
|---|---|---|
| Claude Code | Full | Reference implementation |
| Codex CLI | Partial | Plugin manifest + shared hooks; no eval transcript adapter |
| OpenCode | Partial | JS plugin with bootstrap injection; no eval transcript adapter |
Contributors closing parity gaps should follow harness-parity-check.md: it audits which Slow-powers features are wired up for a given harness and preps an agent to close one gap.
Slow-powers integrates directly into your agent's session, providing a highly disciplined set of technical execution utilities. It enforces strict test-driven development (TDD), systematic scientific debugging, rigorous verification checks, safe workspace isolation via git worktrees, and clean branch-finishing hygiene. It also enhances native agent planning phases with strict rules: banning placeholders, enforcing atomic task granularity, and requiring TDD-first checklists.
Installation differs by harness. If you use more than one, install Slow-powers separately for each.
Don't want to look up the steps? Open the harness you want Slow-powers on and paste this prompt to its agent — it'll read the guide, work out which harness it's in, and do the install for you:
Install the "slow-powers" plugin for the coding-agent harness you are currently
running in. Read the installation guide at
https://github.com/slowdini/slow-powers#installation, determine which harness
this is (Claude Code, Codex CLI, or OpenCode), and follow the matching steps —
run the documented marketplace/install commands for Claude Code or Codex, or add
the package to the `plugin` array in opencode.json for OpenCode. Then tell me
exactly what you changed and what I need to do to finish (e.g. restart the
session so the skills load).
The per-harness instructions below are the source of truth the agent follows — and the reference for installing by hand.
/plugin marketplace add slowdini/slow-powers
/plugin install slow-powers@slow-powers
codex plugin marketplace add slowdini/slow-powers
codex plugin add slow-powers@slowdiniYou can also browse and install it interactively: run codex, open
/plugins, choose the slowdini marketplace, and install slow-powers.
Start a new Codex thread after installing so the bundled skills are loaded.
Slow-powers includes a plugin-bundled SessionStart hook for bootstrap
context. Codex hooks are stable, but plugin hooks must be reviewed and trusted
before Codex runs them.
Add Slow-powers to the plugin array in your opencode.json (global or project-level):
{
"plugin": ["@slowdini/slow-powers-opencode"]
}This installs the latest published version from npm.
Slow-powers provides a set of highly focused, execution-level skills that ensure your agent operates with maximum discipline:
using-git-worktrees— Safely isolates development branches on a separate worktree, keeping your active workspace and protected branches likemainclean.test-driven-development— Enforces a strict RED-GREEN-REFACTOR cycle, ensuring all production code is backed by failing test verification first.systematic-debugging— Guides the agent to locate the root cause of failures via scientific hypothesis testing, avoiding "guess-and-check" thrashing.verification-before-completion— Requires running actual test/build commands and presenting concrete evidence before making any success claims.finishing-a-development-branch— Manages local branch hygiene, runs final test verifications, and cleans up git worktrees.writing-skills— Handles future custom skill authoring and updates.
Testing & Verification — test-driven-development, verification-before-completion
Debugging — systematic-debugging
Workspace & Git Hygiene — using-git-worktrees, finishing-a-development-branch
Meta & Extension — writing-skills
- Test-Driven Development — write tests first, always
- Systematic over ad-hoc — process over guessing
- Complexity reduction — simplicity as a primary goal
- Evidence over claims — verify before declaring success
Flat layout — skills and assets live at root, harness-specific integration lives in top-level directories:
skills/— All slow-powers skillsassets/— Icons and images shared across harnessestests/— Cross-cutting and harness-specific tests.claude-plugin/— Claude Code plugin manifest and hooks.codex-plugin/— OpenAI Codex plugin manifestopencode/— OpenCode plugin.claude-plugin/marketplace.json— Claude Code marketplace registrypackage.json— OpenCode plugin manifest + dev toolingharness-parity-check.md— Instructions for an agent in any harness to audit feature gaps and prep to close one
Releases are cut from dev and tagged from main:
- Merge feature PRs into
devafter CI passes. - When ready to ship, trigger the Release PR workflow with the next
version number. It bumps every manifest via
scripts/bump-version.ts, commits todev, and opens adev → mainPR. - Review the release PR (full test matrix runs on it) and merge.
- Merging to
mainautomatically tagsvX.Y.Z, creates the GitHub release, and publishes@slowdini/slow-powers-opencodeto npm. Notes come from the release PR body, or auto-generated if empty.
See .github/workflows/ for the workflow definitions.
Only one secret is needed. Configure it in Settings → Secrets and variables → Actions:
| Secret | Type | Used by | Scope / permissions |
|---|---|---|---|
RELEASE_PR_TOKEN |
GitHub PAT (fine-grained or classic) | release-pr.yml |
Push to dev (Contents: write) and open PRs (Pull requests: write). Required so the release PR triggers CI — PRs opened by the default GITHUB_TOKEN do not. |
MIT — see LICENSE.