sdd

Plugin sdd from marketplace cyber-sdd in cyberuni/cyber-sdd. Commands read from the repo's manifest — today.

Skills (53)

• align-spec

  Detect and reconcile prose-suite drift across the SDD project spec's nodes — the on-demand, CI-usable complement to the inline spec-gate check; use for corpus audits, post-large-change verification, or CI gating.

• architect-impl-governance

  Partial Skill: invoke by name only

• architect-spec-governance

  Partial Skill: invoke by name only

• blast-estimate

  Partial Skill: invoke by name only — blast-estimate's engine that computes a Mission's blast (low/medium/high) from its touch-set plus the project corpus and lines it up against the hand-typed declared blast — the engine for the blast-estimate node, consumed by the mission-graph's writer. Not trigge

• builder-impl-governance

  Partial Skill: invoke by name only

• builder-spec-governance

  Partial Skill: invoke by name only

• check-field-mandates

  Partial Skill: invoke by name only

• check-partition-quality

  Partial Skill: invoke by name only — project-spec/partition-quality's engine: measures from git history how much parallel work a layout permits, and compares candidate layouts. Opt-in from scaffold-project-spec and the formation loop, and runnable standalone; not triggered by users directly.

• check-plan-safety

  Partial Skill: invoke by name only — plan-brief/check-plan-safety's guard engine against machine-local path leaks in tracked plan artifacts — the CI guard, not triggered by users directly.

• check-plugin-manifests

  Partial Skill: invoke by name only — plugin/check-plugin-manifests' guard engine against a manifest declaring a component the package does not ship — the CI guard, not triggered by users directly.

• check-project-specs

  Partial Skill: invoke by name only — corpus/spec-floor's engine that runs every project-spec check, over the whole corpus or over one project — the commit-floor and CI entrypoint, not triggered by users directly.

• check-retired-terms

  Partial Skill: invoke by name only — retired-terms' guard engine against survivors of a retired path, directory, or naming convention across the whole tracked corpus — the CI guard, not triggered by users directly.

• check-scenario-overlap

  Partial Skill: invoke by name only — project-spec/scenario-overlap's engine that detects the same behavior specified in two nodes' suites across one project spec — feeds the formation Warden, not triggered by users directly.

• check-spec-references

  Partial Skill: invoke by name only — project-spec/check-spec-references' engine that resolves every relative reference in one project spec's markdown and fails on the ones pointing at nothing — run from the per-project CI entrypoint, not triggered by users directly.

• check-spec-structure

  Partial Skill: invoke by name only — project-spec/check-spec-structure's engine that audits a project spec's internal node-shape — feeds the formation Warden, not triggered by users directly.

• collision-ladder

  Internal skill: at a known node-level collision between two missions, descends the finer-than-node ladder (file → region → semantic) to classify the clash hard or soft — a read-only downgrade-only disambiguator, not triggered by users directly.

• combat-log-governance

  Partial Skill: invoke by name only — the SDD combat-log contract, the durable provenance record's shape. Loaded by the conductor, spec-gate, and the doctrine-loop Scanner, not user-triggered.

• concept-index

  Partial Skill: invoke by name only — project-spec/concept-index's engine that derives the by-concept view of a project spec into spec.md — used to re-unify a cross-cutting concern the capability folder tree scatters, not triggered by users directly.

• discover-plans

  Partial Skill: invoke by name only — intake/plan-discovery's engine that surfaces resumable mission plan briefs — used by the sdd gateway on entry, not triggered by users directly.

• discover-specs

  Partial Skill: invoke by name only — corpus/discovery's frontmatter-scanning engine across the SDD spec locations — used by the sdd gateway to scan statuses and by start-mission to locate the project spec, not triggered by users directly.

• doctrine-loop

  Partial Skill: invoke by name only — the SDD doctrine loop, the Strategist's outer loop run by the Scanner — invoked by the doctrine-loop delegate, not triggered by users directly.

• formation-loop

  Partial Skill: invoke by name only — the SDD formation loop, the Architect's outer loop run by the Warden — invoked by the formation-loop delegate, not triggered by users directly.

• gate-validation-governance

  Partial Skill: invoke by name only — the SDD gate-legality contract. Loaded by spec-gate, the conductor, and the spec-judge, not user-triggered.

• impl-producer-governance

  Partial Skill: invoke by name only

• init

  Use this skill to onboard SDD's opt-in repo-scoped conveniences — currently the mission statusline, which surfaces the current mission phase in the Claude Code status line while a mission runs. Trigger on "set up the statusline", "configure the SDD status line", "onboard SDD conveniences", or "init

• lifecycle-governance

  Partial Skill: invoke by name only — the SDD spec lifecycle contract. Loaded by sdd, spec-gate, start-mission, the conductor, and the spec-judge, not user-triggered.

• manage-ignore

  Partial Skill: invoke by name only — intake/manage-ignore's curation engine for the SDD ignore rules — loaded by the manage gateway (Housekeeping), not triggered by users directly.

• manage-scenario-bridge

  Partial Skill: invoke by name only — the curation engine for a project's scenario-bridge.toml — loaded by the manage gateway (Setup & discovery), not triggered by users directly.

• manage-spec-anchors

  Partial Skill: invoke by name only — corpus/spec-anchors' curation engine for SDD's extra spec-discovery anchors — loaded by the manage gateway (Housekeeping), not triggered by users directly.

• manage

  Use this skill when doing manage-level (non-mission) SDD work on the spec corpus — bootstrap, inspect, audit, or housekeeping — such as "set up the project spec", "backfill the spec", "list the SDD specs and statuses", "audit the corpus structure", "check for spec/suite drift", or "retire completed

• mission-graph

  Internal skill: the mission-graph kernel — a git-tracked, append-only work-graph store folded into a ready frontier and a cycles repair view; used by the cyberfleet-batch dispatch loop, not triggered by users directly.

• oracle-spec-governance

  Partial Skill: invoke by name only

• ownership-governance

  Partial Skill: invoke by name only

• pause-mission

  Checkpoint an in-progress SDD mission INTO its plan brief so any later session can pick it up. Use this skill when asked to 'pause', 'wrap up for now', or 'stop here' mid-mission — update the plan's todo statuses and rewrite its ## NEXT anchor so a fresh session continues exactly where you left off.

• place-node

  Partial Skill: invoke by name only — project-spec/place-node's engine that suggests a capability home and surfaces duplicates for a new node — used by explore, not triggered by users directly.

• plan-retirement

  Partial Skill: invoke by name only — the SDD Doctrine loop's last retro step — the gated, idempotent tracked deletion of a retired mission plan. Invoked by the doctrine-loop Scanner, not user-triggered; the clearance contract lives in the body + README.

• plugin-contract-governance

  Partial Skill: invoke by name only — the SDD plugin contract for what a plugin implements. Loaded by the conductor and by plugin authors, not user-triggered.

• remediation-governance

  Partial Skill: invoke by name only — the SDD remediation bar: how a producer responds to a `change` verdict at either gate. Loaded by the spec-producer and the impl-producer, not user-triggered.

• resolve-governances

  Partial Skill: invoke by name only — the SDD governance matcher, resolving which actor-bar governances apply to a touched file — run by the conductor and the cold spec/impl judges, not triggered by users directly.

• resolve-tracking

  Partial Skill: invoke by name only — intake/resolve-tracking's engine that resolves an artifact's tracked-or-ignored signal — run by the conductor at intake, not triggered by users directly.

• resume-mission

  Resume an in-progress SDD mission from its plan brief. Use when asked to 'load the plan', 'resume the mission', 'continue github-NN', or otherwise pick up an SDD .plan.md where it left off — re-establish the working method and spec context, find the next todo, and continue without relitigating settl

• scaffold-project-spec

  Partial Skill: invoke by name only — lay out an SDD project-spec

• sdd

  Use this skill when the user explicitly invokes SDD or wants to work on a creation artifact with Spec-Driven Development.

• solution-producer-governance

  Partial Skill: invoke by name only — the SDD default solution-producer procedure. Loaded in-session by the conductor when it runs the solution-producer role inline, not user-triggered.

• spec-format-governance

  Partial Skill: invoke by name only

• spec-gate

  Partial Skill: invoke by name only — the SDD spec gate (Draft → Approved), the verdict on a CR's spec + suite diff — run by the conductor inside the mission loop, not triggered by users directly.

• spec-producer-governance

  Partial Skill: invoke by name only — the SDD default spec-producer procedure. Loaded in-session by the conductor when it runs the spec-producer role inline, not user-triggered.

• spec-structure-governance

  Partial Skill: invoke by name only — the SDD project-spec organization contract: what kind of node a spec is and where that kind lives. Loaded by scaffold-project-spec, place-node, the formation Warden, and the architect bars, not user-triggered.

• ssa-lowering

  Internal skill: the reasoning front-end that lowers one-or-more change requests into a partitioned set of Missions — one owning Mission per spec-node (SSA) — applying the Oracle (should we?) and Architect (where/barrier?) lenses, resolving same-node contention into ordered versioned-RAW edges, and l

• start-mission

  Use this skill to make a change to an SDD project — triggered by a general change request like "add a start-mission skill to sdd", "implement the auth capability", "revise the gateway spec", or "work on <github issue url>". Opens a change request against the durable project spec and runs the mission

• suite-format-governance

  Partial Skill: invoke by name only

• touch-set-correction

  Internal skill: reconciles a Mission's declared touch-set against what its git diff actually changed — read-only, post-hoc; used to correct the mission-graph's hazard set from prediction to reality, not triggered by users directly.

• verify-scenarios

  Partial Skill: invoke by name only — the Gherkin-scenario-to-test-report bridge verifier — invoked by the impl-judge at the impl gate, not triggered by users directly.

Subagents (5)

• sdd-automaton

  Internal SDD conductor realized headless — the driver spawned when there is no user channel (an unattended scheduler or a multi-CR fan-out). Runs the same mission loop as the in-session conductor (explore → spec gate → deliver → impl gate → handoff): self-asserts at the autonomy bar within leash, ba

• sdd-impl-judge

  Internal SDD impl-judge (default). Grades the implementation against the frozen .feature at the impl gate — re-derives each scenario's oracle independently, runs the impl-producer's verification, and emits per-scenario pass/fail plus a structural read. Spawned cold by the conductor; never user-trigg

• sdd-scanner

  Internal SDD Doctrine-loop delegate (the Strategist's Scanner). Runs the outer loop at lifecycle granularity — drafts unratified strategy from persisted artifacts to the durable ledger for the Council's keep-or-cut. Spawned by name via the doctrine-loop skill; never user-triggered; no user channel.

• sdd-spec-judge

  Internal SDD spec-judge (default). Grades a CR's spec.md + .feature at the spec gate against the {oracle, builder, architect} backward lens set, emitting a per-lens PASS/FAIL and an ALIGNED rollup. Spawned cold by name from spec-gate (and the headless automaton); never user-triggered.

• sdd-warden

  Internal SDD Formation-loop delegate (the Architect's Warden). Runs the structure outer loop corpus-wide and continuous — reads the corpus structure + discovery post-mission and emits a finding set covering every spec (node-shape / split / reconcile), each carrying its own self-clear-or-escalate ver

Similar plugins