superkit

superkit

A Claude Code plugin that fuses spec-kit and superpowers: spec-kit plans WHAT, superpowers controls HOW, superkit decides WHEN / WHICH / IN WHAT ORDER.

Installation

superkit orchestrates two tools, so install both, then the plugin itself.

1. spec-kit — uv tool install specify-cli (then run specify init . --ai claude inside each project you use superkit in).
2. superpowers — in Claude Code: /plugin install superpowers@claude-plugins-official.
3. superkit — add this repo as a plugin marketplace, then install:

   /plugin marketplace add joshuatrobertson/super-kit
   /plugin install superkit
   

   (Or clone the repo and point at the local path: /plugin marketplace add ./super-kit.)

Quick start

1. /superkit:setup — verify dependencies, write the bridging rule, create .superkit/
2. Pick a mode: /superkit:greenfield, /superkit:feature, or /superkit:enhance
3. /superkit:status — see every spec's state and what's next

See docs/superpowers/specs/ for the full design.

Skills

Skill	Trigger	Status	Description
/superkit:setup	Invoke-only	Implemented	One-time setup: verify dependencies, write the bridging rule into spec-kit, create .superkit/ and initialise the registry.
/superkit:greenfield	Invoke-only	Implemented	Define the product, batch-generate specs for every backlog item, then execute them all end-to-end.
/superkit:feature	Invoke-only	Implemented	Spec, plan, and execute a single new feature end-to-end (branch + optional PR).
/superkit:enhance	Invoke-only	Implemented	Brownfield re-spec: update or add a small spec for an existing area, regenerate plan/tasks, and execute.
/superkit:iterate-to-green	Invoke-only	Implemented	After per-task TDD, run the full suite and loop scoped fixes until green or until the stall gate asks how to proceed.
/superkit:escalate-to-workflows	Invoke-only	Implemented	When the loop is stuck, preflight Claude Code dynamic workflows, fan out debugging, and return a patch for the in-session loop to verify.
/superkit:status	Invoke-only	Implemented	Display the live state of every spec in the registry so you know what's done and what's next.
superkit-orchestration	Auto-trigger	Implemented	Route build/spec requests to the right mode and right-size the process so small work is not over-engineered.
respecting-the-spec-contract	Auto-trigger	Implemented	During execution, enforce that tasks.md is the contract and subagents receive only their own task.
superkit:stack-conventions	Auto-trigger	Implemented	Fetch the project stack's current best practices from the web and write a human-confirmed conventions block into the constitution; invoked by setup, re-runnable to refresh.
superkit:conformance-check	Auto-trigger	Implemented	Before review, check the branch diff against spec.md acceptance criteria and surface an advisory met/unmet/uncertain checklist.

When to use which (scale-down)

• < 30 min / < 3 files — just do it; no tooling needed.
• 30 min – 2 h, single concern — use superpowers skills alone (no spec-kit overhead).
• > 2 h or already shipped — full combo: /superkit:feature for a new feature, /superkit:greenfield for a new product.
• Regulated / audited work — full combo mandatory so the spec artefacts exist as a paper trail.

How it works

superkit invokes spec-kit's speckit-* skills and superpowers' skills via the Skill tool. .superkit/registry.md is the source-of-truth index tracking every spec's status; spec artefacts (spec.md, plan.md, tasks.md) stay in spec-kit's specs/<id>/ directories.

See scenario walkthroughs.

End-to-end workflow

Every skill superkit invokes, across all modes, and where the execution-loop additions fire. Nodes marked (NEW) — iterate-to-green and escalate-to-workflows — are introduced by the iterate-to-green design. See docs/workflow.md for the annotated, node-by-node walkthrough.

flowchart TD
    U([User: build / change / spec something]) --> ROUTER{{"superkit-orchestration<br/>route + right-size"}}

    ROUTER -->|"tiny: &lt;30m, &lt;3 files"| TINY([just do it — no tooling])
    ROUTER -->|"not set up here"| SETUP
    ROUTER -->|"new product"| GF_CONST
    ROUTER -->|"one new feature"| BR
    ROUTER -->|"change existing"| ENH_SCOPE

    subgraph SET["/superkit:setup — one-time, idempotent"]
      direction TB
      SETUP["check-deps.sh<br/>(spec-kit + superpowers)"] --> SETUPB["bridging rule → constitution.md"] --> SETUPC["registry.sh init"]
    end
    SETUPC -.->|then pick a mode| ROUTER