DIXI Spec Kit documentation Español · Source on GitHub

/dixi.analyze

Purpose

Analyze spec chain consistency and the impact of a change.

Find gaps and contradictions across goal, domain, module, feature, contract and test, and the impact of the change described in $ARGUMENTS. Report only; no writes.

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

Invocation

Argument: [ID or change description]. 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 check for mechanical rules (IDs, parents, links).
  2. Read the chain declared in .dixi/traceability.json and the specs. Look for: features without contract or tests, unverifiable criteria, contradictions between specs, decisions without ADR and pending markers.
  3. If $ARGUMENTS describes a change, list affected artifacts (specs, contracts, tasks, tests, code) and whether it breaks compatibility.
  4. Order findings by severity and suggest the command that fixes each one (/dixi.clarify, /dixi.specify, /dixi.plan or /dixi.build).
  5. Do not modify files or tests.

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