From superkit
0-to-1 product build — define the product once, write a whole batch of specs up front, then execute the batch with superpowers. Asks how to execute (continuous / sequential / parallel) at execute time.
How this skill is triggered — by the user, by Claude, or both
Slash command
/superkit:greenfieldThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a product from nothing. Run a dependency check first
Build a product from nothing. Run a dependency check first
(bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-deps.sh"); if it fails, route to /superkit:setup.
speckit-constitution to set governing principles (once)..superkit/product.md: the overall what/why plus a feature
backlog — an ordered list of features to spec, each with a short id, title, and any
dependencies. Use AskUserQuestion to decompose if the product is large.bash "${CLAUDE_PLUGIN_ROOT}/scripts/registry.sh" add <id> "<title>" <depends-on>For each backlog item, in dependency order:
git rev-parse --abbrev-ref HEAD.speckit-specify (creates specs/<NNN>-name/ and branch <NNN>-name).
Record spec-path + branch: registry.sh set <id> spec-path <path> and
registry.sh set <id> branch <branch>; registry.sh set-status <id> specified.speckit-clarify → set-status clarified.speckit-plan → set-status planned.speckit-tasks → set-status tasked. Gate: specs/<id>/tasks.md non-empty.git checkout <base>) before the next
item, so specs don't drift across branches.When the backlog is fully specified, run /superkit:status to show the batch.
Ask the user (AskUserQuestion) how to execute:
superpowers:dispatching-parallel-agents, serialize dependents.Then drive superpowers accordingly (using-git-worktrees, test-driven-development,
subagent-driven-development, superkit:iterate-to-green, superkit:conformance-check, requesting-code-review,
finishing-a-development-branch), updating each spec's status (executing → in-review → done)
as you go. Run superkit:iterate-to-green per strategy: continuous = one whole-suite pass
after all specs; sequential = one pass per spec before its review/finish; parallel =
one pass per agent, plus a final whole-suite pass after merges to catch cross-spec regressions.
Do NOT re-plan — each specs/<id>/tasks.md is the contract. Pass each subagent ONLY its
task. Never hand a subagent the whole .superkit/ or specs/ tree.
npx claudepluginhub joshuatrobertson/super-kit --plugin superkitGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.