kborovik

commit

Commit staged git changes w/ descriptive Conventional Commits message. Triggers when user asks to commit, save changes, ∨ mentions GitHub commits. Phrasings: "commit", "save my changes", "commit this".

merge

Merge GitHub PR into main w/ release-ready commit message. Triggers when user mentions merging PR, landing branch, shipping GitHub PR. Phrasings: "merge this", "land the PR", "merge PR #N".

release

Cut SemVer release for single-package repo — bump `version` in detected manifest, commit, create annotated tag `v<x.y.z>`. Local only, ⊥ push, ⊥ GitHub Actions. Triggers when user says "release", "tag", "ship", "cut a version", "bump version".

Data & Documents Listed

issue

Create, file, open, log, ∨ track GitHub issue. Always-gated by `core:socratic` skill — concrete intent passes ≤ 1 turn, vague intent triggers dialogue until convergence. Triggers when user mentions GitHub issues, bug reports, feature requests, ∨ wants to track work on GitHub. Phrasings: "file an issue", "open a bug", "track this on GitHub".

pr

Create GitHub PR from issue number ∨ objective. Triggers when user mentions GitHub PRs, pull requests, opening PR. Phrasings: "open a PR", "create a pull request", "PR for issue #N".

github-release

design-wide

ADHD-internals variant of `sdd:design` — N=5 frame-reframed proposals diverged in isolated parallel sub-agents, then mechanically scored ∧ clustered; top-3 by score seed `## Proposal` as labeled alternatives A | B | C, Open Questions loop converges per sister design skill. Use when user wants wider divergence than single-pass propose-shape can supply, or names ADHD-mode explicitly. Triggers: "/sdd:design-wide", "design-wide <topic>", "ADHD design", "diverge wide on", "show me alternative shapes for", "give me N proposals for", "what else could this look like".

AI & Automation Listed

explain

Math-glyph → prose. Expand any SPEC.md citation into plain English. Read-only. Inverse of the glyph skill (math-glyph encoder). Triggers when human wants to understand a §V invariant, §T task, §B bug, or §I interface without the encoding. Phrasings: "/sdd:explain", "what does §V.<n> mean", "decompress this", "explain in prose", "I don't read math-glyphs". ⊥ for writes — those go through /sdd:spec.

reorganize

SPEC.md §V cluster + renumber + cite-DAG sweep. Operator-triggered manual clarity-shape pass — distinct from /sdd:compact (token reduction). Triggers when operator invokes `/sdd:reorganize` ∨ asks to renumber §V, regroup invariants by topic, ∨ tidy §V order. 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. ⊥ user-invoked — invoked from consumer cmd pre-apply gate (/gh:issue, /sdd:spec).

backprop

Bug → spec protocol. On bug found ∨ test fail → trace cause, decide if new §V invariant catches recurrence, append to §B. Triggers: test failure, bug report, post-mortem, explicit user ask. Phrasings: "X broke", "we got bit by", "post-mortem on Y", "this should never recur", "add a §V for". ⊥ for mechanical typo ∨ one-off fix w/ ⊥ recurrence class — pure code fix only.

AI & Automation Listed

glyph

Math-glyph encoding — LLM-facing compression for SPEC.md ∧ spec-adjacent writes. Loaded by /sdd:spec, /sdd:build, /sdd:check. Triggers on any write to SPEC.md ∨ user says "math-glyph", "glyph", "compress this", "be brief".

Web & Frontend Listed

build

Plan-then-execute impl vs SPEC.md. Triggers when user asks to build, implement, ∨ execute spec ∨ specific §T task. Phrasings: "build §T.<n>", "build --next", "implement next task", "run the build", "does the implementation run?", "is §T.<n> done?".

Data & Documents Listed

check

Read-only drift detector. Diffs SPEC.md vs current code ∧ reports violations grouped by severity. ⊥ writes — suggests remedies via spec ∨ build skills, ⊥ invokes them. Triggers when user asks to check drift, audit spec, verify invariants, ∨ ask if code still matches invariants. Phrasings: "check drift", "audit the spec", "does the code still match invariants", "check invariants", "spec vs code", "is the spec still accurate?", "did the code drift?".

spec

Sole mutator of SPEC.md @ repo root — create, amend, ∨ backprop bugs. Triggers when user asks to write spec, start new spec, distill spec from code, add invariants, amend a section, ∨ record a bug. Common phrasings: "write the spec for...", "new spec", "distill spec from code", "spec this idea", "import existing repo", "pull invariants out of code", "this bug keeps biting", "post-mortem on Y".

Web & Frontend Listed

design

Propose-then-critique structural design loop → draft to `designs/<slug>.md`. Distinct from socratic (which sharpens vague intent). Use when user wants to design a structural change, weigh tradeoffs between named alternatives, propose an architecture, or shape a subsystem before implementation. Triggers: "/sdd:design", "design the X", "shape the X subsystem", "tradeoffs between A and B", "how should we structure", "propose an architecture for".

Web & Frontend Listed

explore

Optional pre-design exploration tool — two-pass layer-primary divergence emitting a tradeoff matrix at `designs/<slug>-explore.md`. Sits ahead of `/sdd:design` in the funnel; matrix feeds `/sdd:design` (when shape choice remains) or `/sdd:spec` direct amend (when bail-out fires on a clearly-dominant layer). Distinct from `sdd:design`: no Open Questions loop, no A|B|C alternatives, ⊥ FOLD-IN candidate. Use when user doesn't yet know what shapes are possible. Triggers: "/sdd:explore", "explore <topic>", "what shapes are possible for", "I don't know what layer to intervene at", "what could this look like", "enumerate options for", "find the right layer for".

compact

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

steno

Human-facing terse-prose register for non-author reviewers. Triggers: write/edit human-facing terse prose for review; user says "steno", "shorthand", "tighten this", "make this shorter".

Data & Documents Listed

rephrase

Rephrase a short piece of text (email, message, post) into 3 concise variants in different registers: Direct, Warm, and Professional. Preserves meaning, strips filler, keeps each variant easy to skim and unambiguous. Triggers on `/rephrase <text>` or explicit asks like "rephrase this", "reword this", "give me 3 versions of this message". Do NOT use for long-form writing, translation, summarization of unrelated content, or code.

0 Updated yesterday