DIXI Spec Kit documentation Español · Source on GitHub

/dixi.domain

Purpose

Design domains, bounded contexts and ubiquitous language.

Delimit the domain given in $ARGUMENTS: contexts, ubiquitous language and modules linked to business goals.

Generated by scripts/build-command-reference.py from the packaged command text; do not edit by hand.

Invocation

Argument: <goal or domain>. Angle brackets mark a required value and square brackets an optional one. In the steps, $ARGUMENTS is the text written after the command.

Example

The text after the command is the request; change it to match your project.

When to use it

Steps

  1. Find the goal or domain (kind: goal or domain) in .dixi/traceability.json; if unclear, ask and stop.
  2. Run dixi workflow prepare domain --target <ID> --request "<summary>" and follow its steps and gates.
  3. Write or update 03-domains/<slug>/domain-spec.md: context boundaries, ubiquitous language, rules and invariants, and proposed modules.
  4. Register the domain (kind: domain, with the goal as parent) and every new module (kind: module, with the domain as parent) in .dixi/traceability.json.
  5. The person confirms boundaries and terms; until then they remain a proposal.
  6. Suggest /dixi.architecture or /dixi.specify.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: files touched, checks (run, failed, not run), open items and the suggested next command.

Next step