Command reference

The grouping follows the process spine: raise work into the discovery backlog, break it down into the delivery backlog, then sprint and review it to done.

Raise

Intake into the discovery backlog: a defect, a proposed change, an unsettled design, or a raw report nobody has diagnosed yet.

Command	Does
`/sdlc-studio bug`	create a bug interactively
`/sdlc-studio bug list`	list bugs (`--status`, `--severity`, `--epic`)
`/sdlc-studio bug fix --bug BG0001`	start fixing
`/sdlc-studio bug verify --bug BG0001`	verify the fix, at a declared depth
`/sdlc-studio bug close --bug BG0001`	close it
`/sdlc-studio bug reopen --bug BG0001`	reopen a closed bug
`/sdlc-studio cr create`	file a change request
`/sdlc-studio cr list`	list them (`--status`, `--priority`)
`/sdlc-studio cr review`	review CR statuses against the implementation
`/sdlc-studio cr close --cr CR-0001`	complete, reject or defer
`/sdlc-studio cr sync`	two-way sync with GitHub Issues (`--dry-run` to preview)
`/sdlc-studio rfc create`	draft an RFC - an unsettled design, with options
`/sdlc-studio rfc list`	list RFCs
`/sdlc-studio rfc review`	flag stalled RFCs and unresolved decisions
`/sdlc-studio rfc accept --rfc RFC-0001`	record the decision, spawn the workstream CRs
`/sdlc-studio rfc close --rfc RFC-0001`	supersede or withdraw
`/sdlc-studio issue create`	file a raw, undiagnosed report

Break down

Discovery to delivery. See the two-backlog model.

Command	Does
`/sdlc-studio refine show --request CR-0001`	is it refinable, and what is in it?
`/sdlc-studio refine apply --request CR-0001`	decompose into an epic and stories, links wired
`/sdlc-studio refine apply --request CR-0002 --into EP-0009`	decompose into an epic that already exists
`/sdlc-studio refine add --request CR-0001`	a later slice of an already-decomposed request
`/sdlc-studio triage show --issue IS0001`	is this issue triageable?
`/sdlc-studio triage apply --issue IS0001`	decompose an issue into the bugs that fix it
`/sdlc-studio epic`	generate epics from the PRD
`/sdlc-studio epic plan --epic EP0001`	preview the epic workflow (`--agentic` for waves)
`/sdlc-studio epic implement --epic EP0001`	execute it
`/sdlc-studio epic review`	cascading review
`/sdlc-studio story --epic EP0001`	generate stories from an epic
`/sdlc-studio story generate`	extract stories from code - brownfield
`/sdlc-studio story plan --story US0001`	plan and test-spec a story
`/sdlc-studio story implement --story US0001`	build it (`--tdd`, `--from-phase`)
`/sdlc-studio story review`	review story status from the codebase
`/sdlc-studio story sync`	push and pull to GitHub Issues

Sprint and review

The delivery loop. See the sprint.

Command	Does
`/sdlc-studio sprint <batch> --goal <rung>`	the goal-driven loop - the primary delivery workflow
`/sdlc-studio sprint plan`	select, order and size a batch
`sprint.py breakdown <batch>`	the grooming census, read-only
`sprint.py preflight --retro RETRO0001`	every refusal the close would raise, read-only
`/sdlc-studio sprint close --retro RETRO0001`	the close chain (`--apply-signoff --principal`)
`/sdlc-studio sprint boundary --retro RETRO0001`	close this cycle, open the next
`/sdlc-studio sprint report --id RETRO0001`	the end-of-sprint report and its checklist
`/sdlc-studio sprint decision defer` / `list` / `resolve`	set a unit aside pending your ruling
`/sdlc-studio handoff generate`	where to pick up a run that stopped short
`/sdlc-studio review`	unified PRD, TRD and TSD review (`--quick`, `--focus`)

The levers

The documents that steer everything else, and the people who speak for them.

Command	Does
`/sdlc-studio prd create` / `generate` / `review`	the PRD - authored, or extracted from code
`/sdlc-studio trd create` / `generate` / `review`	the TRD
`/sdlc-studio trd visualise`	regenerate the C4 architecture diagrams
`/sdlc-studio trd containerize`	add container design decisions
`/sdlc-studio tsd` / `tsd generate` / `tsd review`	the TSD
`/sdlc-studio pvd create` / `pvd sync` / `pvd drift`	the PVD, for a product spanning repos
`/sdlc-studio persona create` / `generate` / `list` / `review`	the team and the design personas
`/sdlc-studio persona import`	bring personas in from elsewhere
`/sdlc-studio consult team [artefact]`	a Three Amigos review
`/sdlc-studio consult stakeholders [artefact]`	the wider cast, with their veto lines
`/sdlc-studio chat [persona]`	talk to a seat
`/sdlc-studio chat --workshop [topic]`	a multi-persona discussion

Support

Keeping the backlog honest and visible.

Command	Does
`/sdlc-studio status`	the dashboard - what is specified, built, proven, checked (`--full`, `--brief`, `--testing`)
`/sdlc-studio hint`	the single next thing to do
`/sdlc-studio reconcile`	detect and fix status and count drift (`--dry-run`, `--scope`)
`/sdlc-studio reconcile --verify`	run the acceptance criteria and update the stamps
`/sdlc-studio gate`	the quality gate (`--release`, `--require-retro`, `--only`, `--skip`)
`/sdlc-studio audit`	the adversarial pressure-test
`/sdlc-studio audit --profile repo`	the same hunt on an untouched repository, zero setup
`/sdlc-studio decisions add` / `list` / `promote`	the project decisions log
`/sdlc-studio lessons recall` / `add` / `list` / `rank`	failure memory (`--global` to promote)
`/sdlc-studio lessons revalidate` / `summary` / `prune`	keep it from rotting into noise
`/sdlc-studio retro create` / `validate` / `dispose` / `extract`	the retrospective

Utility

Setting up, writing code, testing, migrating, shipping.

Command	Does
`/sdlc-studio init`	initialise the project (`init guided` is the front door)
`/sdlc-studio help`	the command reference, in your agent
`/sdlc-studio code plan` / `implement` / `review` / `verify`	the code workflow (`--tdd`, `--story`, `--epic`)
`/sdlc-studio code test` / `check` / `refactor`	run tests, lint with auto-fix, guided refactoring
`/sdlc-studio test-spec` / `generate` / `review`	test specifications
`/sdlc-studio test-automation`	generate executable tests (`--spec`, `--type`, `--framework`)
`/sdlc-studio test-env setup` / `up` / `down` / `status`	containerised test environments
`/sdlc-studio mutation`	prove the tests can fail
`/sdlc-studio repo map build` / `query` / `stats`	index the codebase so the agent reads the right files first
`/sdlc-studio deploy`	the deploy last mile - gate, verify, record. Operator-triggered, never autonomous
`/sdlc-studio migrate`	review every artefact and upgrade what is safe (dry-run; `--apply`)
`/sdlc-studio project upgrade`	upgrade a consuming project’s artefacts and conventions
`/sdlc-studio skill-update`	upgrade the installed skill itself
`/sdlc-studio project plan` / `implement`	run whole epics in dependency order (`--agentic` for waves)
`/sdlc-studio project sync`	sync CRs, stories and epics with GitHub Issues
`/sdlc-studio plan list` / `archive`	manage Claude Code plan files

Deterministic artefact tooling

The scripts the sprint drives. Run them directly when you want the mechanical thing done the same way every time - and reach for one before doing anything mechanical by hand.

Script	Does
`artifact.py new --type <type> --title ...`	create any numbered artefact: collision-free id, valid scaffold, index row, parent wiring, provenance stamps
`artifact.py batch --type <type> --count N`	reserve an id range and write N pre-wired scaffolds atomically
`artifact.py close --id <ID> --verdict approve`	terminal-transition an artefact and record telemetry
`next_id.py allocate --type <type>`	the next collision-free id (`--remote` also considers `origin/main`)
`verify_ac.py run --id US0001`	execute a unit’s acceptance criteria
`transition.py set <id> <status>`	change status through the gate rather than by editing a line
`file_finding.py file --type bug --fields-file ...`	file an audit finding; refuses a hollow artefact
`provenance.py check` / `remake`	flag artefacts not created by the tool
`telemetry.py show`	per-run outcomes - local only, gitignored

Where to next

Configuration - the keys that change what these commands enforce.
The sprint - the workflow most of these serve.
FAQ - what the artefact types mean, in plain language.