Part 55: CLI Plugin Spec📋

List and Graph📋

Every analyzer spec and every codegen spec across the corpus names a parentRequirement: string — pointing at a canonical Requirement living in ddd-spec. Without a way to inspect the catalogue of Requirements, the references drift. @frenchexdev/ddd-cli-plugin-spec exposes two verbs that surface the catalogue and its relationships.

The Two Tasks📋

spec:list — print every canonical Requirement the corpus declares. The output is the full list (alphabetical, with the parent subpath like strategic / application / secondary / saga), suitable for piping into grep to find Requirements matching a partial name.

spec:graph — print the @Refines relationship graph. The corpus's Requirements can refine each other (X @Refines Y means X is a more specific version of Y), and the graph is what a stakeholder reads to understand what does this corpus claim to formalise. The output format is the same Mermaid-fragment shape the context-relationship codegen emits, so consumers can compose the requirement graph into a docs site.

Both tasks read from ddd-spec (Part 60) — the canonical Requirement registry — and produce text the operator inspects or pipes into other tools.

Cross-Links📋

• Reads from Spec Kernel — the canonical Requirement registry lives in ddd-spec; the Feature registry in ddd-spec-features.
• Feeds the Compliance plugin — the Requirements listed by spec:list are the rows of the compliance matrix.
• Built on CLI Framework + CLI Kernel.

Back to the series index.