spec-driven-development

Umbrella catalog of the project's Mermaid class-diagram conventions (domain, commands, queries, ops kinds), organized by theme. Each theme lives in a sibling folder's index.md. Load when AUTHORING, editing, or REVIEWING a diagram in this project — the docs give the canonical authoring rule and the matching review lens (what is canonical and must not be flagged).

Umbrella catalog of all rest-api-spec pattern references. Each pattern lives in a sibling folder of this file — `<pattern-name>/` containing `index.md` (the pattern doc) plus an optional `examples.md` companion. Load to resolve pattern names to their reference docs by path instead of per-pattern skill invocations.

Initializes the project-wide application-layer scaffolding (project package discovery, src/<pkg>/application/, src/<pkg>/infrastructure/, src/<pkg>/infrastructure/services/, src/tests/fakes/, and a minimal src/tests/conftest.py). Invoke with: /application-spec:init-application

Initializes the project-wide domain scaffolding (project package discovery, src/<pkg>/domain/ with shared/, src/tests/ with conftest and unit/). Aggregate-agnostic — run once per project before any @domain-spec:code-generator invocation. Invoke with: /init-domain

Initializes the project-wide messaging scaffolding (project package discovery, src/<pkg>/messaging/ as an empty aggregator package, and a canonical Click __main__.py skeleton). Invoke with: /messaging-spec:init-messaging

Initializes the project-wide persistence scaffolding. Invoke with: /init-persistence

Initializes the project-wide REST API scaffolding. Invoke with: /rest-api-spec:init-rest-api

Umbrella catalog of the reference Python modules the spec pipeline copies verbatim into a target repo during init/scaffold (shared domain primitives, persistence context packages, REST serializers). Each group is a sibling folder of this file. Load to resolve the modules directory and copy a group by path.

Applies a targeted change (add/modify/remove attribute, method, class, or relationship) to an existing Mermaid class diagram. Invoke with: /edit-diagram <diagram_file> <task>

Surgically updates the application service specs (`commands.specs.md`, `queries.specs.md`, `services.md`) from domain/diagram changes. Invoke with: /application-spec:update-specs <domain_diagram>

Cross-plugin naming and layout conventions for diagrams and spec artifacts. Defines the canonical aggregate stem, diagram filenames, and per-plugin sibling folder layout.

Umbrella catalog of all application-spec pattern references. Each pattern lives in a sibling folder of this file — `<pattern-name>/` containing `index.md` (the pattern doc). Load to resolve pattern names to their reference docs by path instead of per-pattern skill invocations.

Umbrella catalog of all domain-spec DDD pattern references. Each pattern lives in a sibling folder of this file — `<pattern-name>/` containing `index.md` (the pattern doc) plus optional `template.md`/`examples.md` companions. Load to resolve pattern names to their reference docs by path instead of per-pattern skill invocations.

Umbrella catalog of all messaging-spec pattern references. Each pattern lives in a sibling folder of this file — `<pattern-name>/` containing `index.md` (the pattern doc). Load to resolve pattern names to their reference docs by path instead of per-pattern skill invocations.

Surgically updates the messaging consumer input specs (`<stem>.messaging/<consumer>.md`) after a domain or commands-diagram change. Invoke with: /messaging-spec:update-specs <domain_diagram>

Umbrella catalog of all persistence-spec pattern references. Each pattern lives in a sibling folder of this file — `<pattern-name>/` containing `index.md` (the pattern doc). Load to resolve pattern names to their reference docs by path instead of per-pattern skill invocations.

Surgically updates the command repository spec after a domain diagram change — regenerates the snapshot sections from the current diagram, appends delta-driven migration rows to §2.Migrations, and emits the persistence updates report. Invoke with: /persistence-spec:update-specs <domain_diagram>

Surgically updates the REST API resource spec after a domain, commands-diagram, or queries-diagram change. Invoke with: /rest-api-spec:update-specs <domain_diagram>

Umbrella catalog of the cross-layer spec-update detector report schemas (domain, application-service axis, ops). Each schema lives in a sibling `<layer>/index.md` folder of this file. Load to resolve the report schema the cross-layer update cascade's detectors emit and downstream layers parse.

Application-layer code updater — the gather → implement → review flow that propagates commands/queries and ops deltas into the application service source. Invoke with: /application-spec:update-code <domain_diagram> [--review]

Domain-layer code updater — the gather → implement → review flow that propagates `<stem>.domain/updates.md` into the domain package source. Invoke with: /domain-spec:update-code <domain_diagram> [--review]

Messaging-layer code updater — the gather → implement → review flow that propagates consumer deltas into the messaging consumer-package source. Invoke with: /messaging-spec:update-code <domain_diagram> [--review]

Persistence-layer code updater — the gather → implement → review flow that propagates domain/persistence deltas into the command-side repository source, plus the query-side repository patches. Invoke with: /persistence-spec:update-code <domain_diagram> [--review]

REST-API-layer code updater — the gather → implement → review flow that propagates resource deltas into the API endpoint/serializer source. Invoke with: /rest-api-spec:update-code <domain_diagram> [--review]

Propagates a diagram change into generated source code across every layer by running each layer's /…-spec:update-code in dependency order (domain → {persistence, application} → {rest-api, messaging}), skipping layers that were never generated. Invoke with: /spec-core:update-code <domain_diagram> [--review]

Surgically updates DDD class specs after a diagram change by detecting deltas, regenerating only affected categories, splicing them into the existing siblings, refreshing exceptions, and conditionally replanning tests. Invoke with: /update-specs <domain_diagram>

Propagates a diagram change across every generated spec layer by running each layer's /…-spec:update-specs in dependency order (domain → {persistence, application} → {rest-api, messaging}), skipping layers that were never generated. Invoke with: /spec-core:update-specs <domain_diagram>

Orchestrates end-to-end application generation for an aggregate diagram by spawning the application-spec:specs-generator and then application-spec:code-generator agents. Invoke with: /application-spec:generate-application <domain_diagram>

Orchestrates end-to-end domain generation for an aggregate diagram by spawning the domain-spec:specs-generator and then domain-spec:code-generator agents. Invoke with: /domain-spec:generate-domain <domain_diagram>

Orchestrates end-to-end messaging generation for a single consumer by spawning the messaging-spec:specs-generator and then messaging-spec:code-generator agents. Invoke with: /messaging-spec:generate-messaging <domain_diagram> <consumer_name>

Orchestrates end-to-end persistence generation for an aggregate diagram by spawning the persistence-spec:specs-generator and then persistence-spec:code-generator agents. Invoke with: /persistence-spec:generate-persistence <domain_diagram>

Orchestrates end-to-end REST API generation for an aggregate diagram by spawning the rest-api-spec:specs-generator and then rest-api-spec:code-generator agents. Invoke with: /rest-api-spec:generate-rest-api <domain_diagram>

Derives the query part of a domain diagram (Query<X>Repository, <X>Info, nested *Info, <X>Filtering, Brief<X>Info, <X>ListResult) from its command part, interviews the user on the divergence decisions, and writes it in place. Invoke with: /derive-query-part <diagram_file>

Rules for deriving the query part of a domain diagram (Query<X>Repository, <X>Info, nested *Info, <X>Filtering, Brief<X>Info, <X>ListResult) from the command part.

Discovers every agent and skill inside a plugin directory and dispatches the `description-trimmer` agent on each one to shrink overly verbose frontmatter descriptions. Use when the harness warns about large cumulative agent or skill descriptions, or when bulk-cleaning a plugin's metadata. Invoke with: /trim-descriptions <plugin_dir>

Discovers pattern files in a folder, interviews the user per-pattern to collect metadata, then spawns skill-from-pattern agents to convert each selected pattern into a skill. Invoke with: /convert-patterns <patterns_dir> <plugin_dir>