sdd

Plugin sdd from marketplace spec-driven-dev in kborovik/spec-driven-dev. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• release

  REPO-LOCAL gh release flow for the sdd plugin — bump `.claude-plugin/plugin.json` version, commit, tag `v<version>`, publish GitHub release w/ generated notes. Triggers: "/release", "cut a release", "publish a release", "bump version and tag", "ship a new sdd version", "gh release".

• backprop

  Bug → spec protocol: trace cause, decide if a new §V invariant catches the recurrence class, append §B. Not user-invoked — engaged from /sdd:spec BACKPROP mode (bug → spec user route = `/sdd:spec <intent>`). Not for mechanical typo or one-off fix w/ no recurrence class — pure code fix only.

• check

  Read-only drift detector. Diffs SPEC.md vs current code, reports violations grouped by severity. Writes nothing — suggests remedies via spec or build skills; never invokes them except green-path chain (clean → build --next). Triggers when user asks to check drift, audit spec, or verify invariants. P

• condense

  SPEC.md condenser — token-budget sweep. Triggers when user invokes `/sdd:condense` or asks to condense spec or /sdd:check emits `## advisory` token-budget overflow line. Phrasings: "/sdd:condense", "condense SPEC.md", "SPEC too big", "shrink the spec", "token budget".

• design

  SDD structural design: propose-then-critique via Claude Code plan mode → approved plan opens a GitHub issue (class label) then stops. Later fold via `/sdd:spec github issue N`. Exhausts structural Open Questions (distinct from socratic "enough"). Use when user wants to design a structural change, we

• explain

  Telegraph → prose. Expand one SPEC.md citation into plain English. Read-only; inverse of telegraph skill (telegraph encoder). Triggers: "/sdd:explain", "what does §V.<n> mean", "decompress this", "explain in prose", "I don't read telegraph". Writes → /sdd:spec.

• github

  Auto-fire gh-CLI workflow governor. Fires when an sdd skill or the operator runs a GitHub issue or pull-request operation — open an issue, start work on one, open a PR, push an issue-linked branch with an open PR, mark a PR ready, merge a PR, or close one unmerged. Shapes the gh workflow: generic is

• monitor

  Auto-fire skill-deviation capture. Fires when, mid-skill-run, an sdd skill misbehaves: instruction ambiguous or self-contradictory, a recipe loop step impossible as written, a prescribed tool/flag fails, or the user corrects the skill's behavior. Redacts, dedups, then operator-gates a GitHub issue o

• reorganize

  SPEC.md §V cluster + renumber + cite-DAG sweep. Operator-triggered clarity-shape pass — distinct from /sdd:condense (token reduction). Phrasings: "/sdd:reorganize", "reorganize the spec", "regroup §V by topic", "renumber invariants", "cluster §V rows", "tidy §V order", "taxonomy pass".

• socratic

  Parameterized single-question intent-sharpening gate. Not user-invoked — engaged from consumer cmd pre-apply gate (e.g. /sdd:spec).

• spec

  Sole semantic author of SPEC.md @ repo root — create, amend, fold designs, fold GitHub issues, or backprop bugs (§T status-flip → build, archive → condense, §V renumber → reorganize; those carve-outs not authoring paths). Triggers when user asks to write spec, start new spec, distill spec from code,

• steno

  Simple technical language for human readers — terse-prose register for non-author reviewers. Not user-invoked — engaged from caller recipes when writing human-facing terse prose (GitHub issue/PR bodies, commit-message bodies, README scan prose).

• telegraph

  Telegraph encoding — LLM-facing compression for SPEC.md and spec-adjacent writes. Loaded by /sdd:spec, /sdd:build, /sdd:check when any write to SPEC.md or spec-adjacent telegraph surface is required. Not user-invoked — engaged from caller recipes (spec, build, check).

Similar plugins