| name | ssot-issue |
| description | Manage issue entities with full CLI coverage, including planning, release-blocking semantics, and close/reopen lifecycle transitions. |
SSOT Issue
Use this skill for issue-only operations.
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
issue create|get|list|update|delete|link|unlink|plan|close|reopen
Workflow
- Inspect issue state and linked impact surfaces.
- Update issue metadata, severity, and release-blocking flags.
- Plan or close/reopen according to current delivery state.
Operating rules
- Treat release-blocking issues as gating artifacts for certification.
- Keep linked feature/claim/test/evidence/risk context accurate.
- If the request spans boundary/release progression, escalate to
$ssot-e2e-change-orchestrator.
Example
ssot issue get . --id iss:demo.login.blocker
ssot issue plan . --ids iss:demo.login.blocker --horizon current
ssot issue close . --id iss:demo.login.blocker
