Commands and skills
| Command | What it does | Invoked by |
|---|---|---|
/setlist:new |
Bootstraps an empty directory: interview, decisions for your approval, the two-phase stamp. | You only |
/setlist:retrofit |
Inventories an existing codebase read-only, then fits the framework around what exists. | You only |
/setlist:upgrade |
Migrates an instance to the bundled edition on one docs-only chore branch, gates unchanged. | You only |
/setlist:gate |
Runs a roadmap stage-gate transition against the stage's exit criteria. | You only |
/setlist:checkpoint |
Spec-scoped Git: the branch, commits with secret and style checks, the close checklist, the --no-ff merge. |
You, or the model when about to commit |
/setlist:validate |
Health-checks the instance and reports findings, fixing nothing without approval. | You, or the model at a transition gate |
/setlist:board |
Reads the trunk and the remote: every spec by state with its driver, branch and age, and the collisions it can see. Refuses nothing. | You, or the model before a flip |
/setlist:journal |
Writes the numbered journal entry for a substantive session. | You, or the model after a substantive session |
/scaffold is no plugin command: /setlist:new generates it as a project-local skill. It wires the test harness, makes the first commit and arms the git hooks by setting core.hooksPath and merge.ff. Five reference skills load by themselves when they apply:
| Skill | Loads when | Carries |
|---|---|---|
model-ladder |
A session weighs escalating | The escalation rules between model tiers |
planner-discipline |
Planning starts | The operating loop, the read budget, park-do-not-improvise |
spec-authoring |
A spec is being written | The spec template and the Closing report contract |
design-surface |
UI work routes through a design intake | The intake on /design, locked redlines committed as spec contracts, design QA on the branch |
diagrams |
A diagram is drawn or synced | The routing test, the drawing rules, five type references |
For UI work the design surface is Claude Code's /design. A design intake drafts the screens as artboards on a design canvas on claude.ai, and you pick one per screen.
The locked redline, the picked artboards' exports and every decision the canvas's comments record are committed under docs/design/ before the spec that builds to it goes ACTIVE, and design QA reads that committed redline. /design needs an interactive session signed in with a claude.ai account and the Design template on; without it, a mock made another way is committed by the same rule.