speckit-superpowers-bridge skill
A bridge hands tasks from Spec Kit to Superpowers discipline: Spec Kit writes what to build, Superpowers enforces how.
- 54 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The extension installs hooks and scripts under `.specify/` and writes a handoff state file.
Install
- Works in
Manual install
specify extension add speckit-superpowers-bridge --from https://github.com/lihan3238/speckit-superpowers-bridge/releases/latest/download/speckit-superpowers-bridge.zipRun it after `specify init my-project --integration claude` or `--integration codex`.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The extension installs hooks and scripts under `.specify/` and writes a handoff state file.
This is third-party code. Review the repository files before installing.
What it does
speckit-superpowers-bridge is a handoff layer between Spec Kit design artifacts and Superpowers implementation discipline. Spec Kit stays the source of truth for the project: constitution, spec, plan and tasks. Superpowers executes tasks, verifies and reviews code and finishes the branch. The bridge connects them through a `.specify/superpowers-handoff.json` file read by identical skills for Claude Code and Codex. The extension has three commands and five hooks. After `/speckit-tasks` the `after_tasks` hook fires and the bridge records the `executing` status. Then `/speckit-superpowers-bridge` in Claude Code or `$speckit-superpowers-bridge` in Codex turns `tasks.md` into a disposable `Task N` list for `superpowers:executing-plans`, then runs verification and review. There is no daemon, service or database.
Who it is for. Developers who run a project through Spec Kit and want Superpowers to drive implementation without replanning.
Good fit when
- The spec and tasks are ready in Spec Kit and execution should go to Superpowers with verification and review.
- Claude Code and Codex use the same handoff contract on one project.
- You work on Windows, Linux and macOS with one ZIP and separate script variants.
- Before a release you check extension readiness with `bridge-status --readiness`.
Not a fit when
- You need a workflow without Spec Kit or without Superpowers, since the bridge connects these two.
- You need your own development discipline, which the bridge does not add.
- The project does not use `specify` and Spec Kit extensions.
Example request
The tasks in `tasks.md` are ready. Run the bridge, hand them to Superpowers for execution and finish with verification and code review.Limitations
The bridge is verified against Spec Kit 1.0.12 and Superpowers 6.4.2, and behavior on other versions is not guaranteed. Linux bash and Windows PowerShell 5.1 and newer are verified in the release sandbox, while macOS passes CI checks without a published-artifact run on a local machine. Claude Code is confirmed on local version 2.1.283 and Codex CLI on 0.157.1. On older Windows with a GBK console you may need `PYTHONUTF8=1`. The extension adds no discipline of its own beyond Superpowers.
How to disable. Remove the extension with a Spec Kit command, for example `specify extension remove speckit-superpowers-bridge`, and delete `.specify/superpowers-handoff.json` if no longer needed.
FAQ
What does the bridge do?
Hands `tasks.md` from Spec Kit to native Superpowers execution without replanning. The handoff contract lives in `.specify/superpowers-handoff.json`.
How do I call the bridge?
With `/speckit-superpowers-bridge` in Claude Code or `$speckit-superpowers-bridge` in Codex, usually after `/speckit-tasks`.
Is a separate service needed?
No. The project has no daemon, service, database or second workflow engine, only commands, hooks and scripts.
How do I check readiness?
With `bash .specify/extensions/speckit-superpowers-bridge/scripts/bash/bridge-status.sh --readiness --actor codex`. A `--json` variant exists.
What if the idea is vague?
Run `superpowers:brainstorming` before `/speckit-specify`: the bridge allows it before the spec, and the design doc can feed the spec.
Discussion
No questions or reviews yet.
Related
SkillsSpec Kit skills for Claude Code, Codex, Cursor, Copilot and OpenCode: specify, plan, tasks, implement, baseline of existing code
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
speq drives spec-driven development in Claude Code and Codex: mission, plan, implement and record into a permanent library.
A skill that runs a long task as a package with verifiable steps and on-disk state, so work resumes in a new session.
A VS Code extension for Spec Kit that renders specs as pages, follows each run and keeps a record of the assistant's decisions.
A methodology and CLI for single-spec development: skills install into a project and lead an agent from idea to verified code
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| speckit-superpowers-bridge (this card) | no | 54 | |
| Spec Kit | no | 149,633 | difference: `spec-kit` defines design, while the bridge hands its tasks to Superpowers |
| Superpowers | no | 316,679 | difference: `superpowers` defines implementation discipline, while the bridge feeds it tasks from Spec Kit |
README in short
The README describes the handoff principle, a capability table, a seven-step quick start, platform support with verification levels and version history up to 1.3.0.