DIXI Spec Kit documentation Español · Source on GitHub

/dixi.change

Purpose

Propose a change to a feature with its impact.

Turn the change described in $ARGUMENTS into a proposal with its impact, before touching specs or code.

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

Invocation

Argument: <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. If $ARGUMENTS is empty, ask for the change description and stop.
  2. Run dixi check and analyze the affected chain in .dixi/traceability.json: specs, contracts, tasks, tests and code.
  3. Write 05-features/<slug>/changes/CHANGE-NNN.md with: motivation, proposed change, affected artifacts, compatibility, new tests needed and risks.
  4. Frozen tests are not edited: if the change contradicts one, the proposal flags it and the person decides.
  5. Do not modify specs or code until the person accepts the proposal; then continue with /dixi.specify, /dixi.plan and /dixi.tasks.
  6. Record the person's decision in the proposal.

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