Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/cyberuni/cyber-sdd --skill builder-spec-governanceLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Affichage de SKILL.md
| name | builder-spec-governance |
| description | Partial Skill: invoke by name only |
| user-invocable | false |
| metadata | {"actor":"builder","gate":"spec","compose":"union"} |
The Builder bar at the spec gate: is this capability fully and testably specified? Judges
the capability's contract (read from its spec + suite), not the document's prose — that is
sdd:spec-format-governance. Loaded by both faces. The SDD default for the builder spec bar; a
plugin may bind its own, and this loads when the registry leaves builder/spec unbound.
sdd:suite-format-governance). For a fold
node whose rule combines two or more interacting sub-conditions, the CFG is drawn from that rule
stated in closed form (single-condition folds may be by example — demanding closed form of one
is over-firing), and its coverage is backed by a mutation sweep and a safety dual
(sdd:suite-format-governance).sdd:spec-format-governance), and the CFG is the single source the scenarios derive from —
so an extension earns its scenario by being a path in the graph, never as a second rule
alongside the edge coverage above. The check is therefore: does the CFG contain a path to each
stated extension? An extension with no path is a hole in the graph — fix it there, and the
standing 1:1 edge coverage supplies the scenario. Never derive a scenario from the prose
directly: a suite drawn from a stated list is 1:1 with that list by construction and can no
longer surface a hole, which is the retrofit shape that has diverged in this corpus before. A use
case declaring extensions: none asserts nothing can diverge — judge that claim against the
graph. A forbidden combination is the same rule in guard form: it is a decision the CFG must
carry, and its refusal scenario comes from that guard's edge..feature, carried as a judge-only @rubric scenario.@rubric dimension or its cut is
justified by a measurement (an ablation Δ, a discrimination count), that measurement is admissible
only if it is not solely the author's own — independently produced/reviewed by a non-author, or a
fresh-adversarial ablation. An author's own instrument silently assumes the property under test. The
standard is stated canonically at sdd:doctrine-loop; this bar requires it be met, not re-listed
(the cold-instrument doctrine).extensions: none is a claim to judge; a forbidden combination is a guard the
graph carries..feature.sdd:doctrine-loop); the cold-instrument doctrine.