DIXI Spec Kit documentation Español · Source on GitHub

/dixi.architecture

Purpose

Propose design and architecture decisions as ADRs.

Propose the design for the target in $ARGUMENTS with alternatives, consequences and ADRs.

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

Invocation

Argument: <domain, module or feature ID>. 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. Run dixi workflow prepare architecture --target <ID> --request "<decision to make>" and follow its steps.
  2. Read the target's specs and the existing ADRs in 09-architecture/adr/; do not contradict an accepted one without flagging it.
  3. For each structural decision write 09-architecture/adr/ADR-NNN-<slug>.md with context, at least two alternatives, proposed decision and consequences. Status: "Proposed".
  4. No ADR becomes "Accepted" without the person's explicit validation; record who validated it and when.
  5. Link the ADR from the affected specs.
  6. Suggest /dixi.contract, /dixi.threat-model or /dixi.plan.

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