| name | ssot-adr |
| description | Manage ADR entities with full CLI coverage, including create/update/status/supersede/sync and reservation flows. Use for ADR-focused operations that should stay within the ADR surface. |
SSOT ADR
Use this skill for ADR-only work.
Command discipline
- Do not spend turns rediscovering syntax with
--help during normal SSOT work. Use the command surface and examples in this skill directly.
- Pick one verified CLI rail for the repo (
ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.
- Only inspect parser or help text when the user explicitly asks about the CLI surface or when observed runtime behavior contradicts the command patterns documented here.
Command surface
adr create|get|list|update|set-status|supersede|delete|syncadr reserve create|list
Workflow
- Inspect with
adr get or adr list.
- Mutate content/status with
adr update or adr set-status.
- Use
adr supersede for lineage instead of deleting historical ADRs.
- Run
adr sync after document edits that should refresh registry metadata.
Operating rules
- Preserve ADR lineage and status history.
- Prefer reserve flows before creating numbered ADRs when ranges are constrained.
- If the request includes SPEC + feature + boundary + release lifecycle steps, escalate to
$ssot-e2e-change-orchestrator.
Example
ssot adr get . --id adr:1001
ssot adr update . --id adr:1001 --title "Updated ADR title"
ssot adr set-status . --id adr:1001 --status approved --note "Approved for current release scope"
ssot adr sync .
