DIXI Spec Kit documentation Español · Source on GitHub

/dixi.constitution

Purpose

Create or amend the project's principles (its constitution), versioned.

Create or amend 00-governance/principles.md, the project's constitution: the few principles every other operation reads before acting, with the change described in $ARGUMENTS. Governance only; no code, specs or tests change here.

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

Invocation

Argument: [principles to add or change, or empty to review]. 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. Read 00-governance/principles.md if it exists, 00-master-spec.md, 01-business/vision.md and the ADRs that cite a principle. If the file does not exist, create it with: purpose, a Version: X.Y.Z line and a Last amended: YYYY-MM-DD line, the principle tables (vision P-NN, architecture A-NN, engineering E-NN, each with "what it means in practice"), the precedence order when principles conflict, how a principle changes, and a ## Change log section.
  2. Apply only the change requested. Keep existing IDs; a retired principle keeps its ID, marked as retired, never reused. Use {{pending: …}} for any value the person has not decided; do not invent principles.
  3. Version the document: MAJOR when a principle is removed or redefined incompatibly, MINOR when one is added or materially extended, PATCH for wording that does not change meaning. Add a dated line to ## Change log with the version, the change and its reason.
  4. List the impact: specs, plans, tasks, ADRs, templates and agent instructions that cite or contradict a changed principle. Do not edit them here; propose the operation that updates each one.
  5. A change that removes or redefines a principle is a structural decision: draft the ADR in 09-architecture/adr/ as "Proposed" and stop until the person approves it.
  6. Suggest /dixi.analyze to find documents that now conflict with the principles.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

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

Next step

No fixed next operation; /dixi.status suggests one.