Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/cyberuni/cyber-sdd --skill architect-spec-governanceThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | architect-spec-governance |
| description | Partial Skill: invoke by name only |
| user-invocable | false |
| metadata | {"actor":"architect","gate":"spec","compose":"union"} |
The Architect bar at the spec gate: does this capability fit the project's structure, and
is its control-flow graph (CFG) well-placed? Judges the capability (read from its spec + suite), not
the document's prose — that is sdd:spec-format-governance. The SDD default for the architect spec bar;
a plugin may bind its own per artifact-type, and this loads when the registry leaves architect/spec
unbound.
spec.md placement map
(sdd:spec-structure-governance): under the screaming-architecture default a capability lives in a
folder named for its intent, while a project that declared mirror-source is correctly placed when
it mirrors its source. But the declaration is not a licence — layouts are ranked by whether
they keep node <-> capability 1:1, because the mission scheduler cuts one mission per node and a
scattered capability degrades the schedule toward serial (ADR-0025). One capability per node,
never smeared across nodes, holds under every strategy, and a layered / framework-first top
level stays discouraged however it is declared.sdd:spec-format-governance), so each is an edge the graph must actually contain. An extension
named in ## Use Cases with no path to it in ## Control Flow is a dangling branch read from
the other side — the prose claims a divergence the drawn graph cannot take. A forbidden
combination of surface elements is the same defect in guard form: if two elements may not be
combined, the graph carries the decision that refuses them, or the constraint is unenforceable and
the prose is decoration. Judge the graph against the stated extensions in both directions —
an edge with no extension is the ordinary uncovered-edge case; an extension with no edge is this
one.The two faces read different inputs. Forward (solution-producer): self-aligns the ungated
<unit>.solution.md, where structure is chosen. Backward (cold spec-judge): grades structure
from spec.md + the suite only — the solution is out of view (grader independence).
sdd:spec-structure-governance), not a preferred
one; one capability per node either way, never smeared across nodes.