DIXI Spec Kit documentation Español · Source on GitHub

/dixi.converge

Purpose

Compare the code with the feature's specs and append traced convergence tasks.

Compare what the code does today with the spec, contracts, plan, tasks and principles of the feature in $ARGUMENTS, and turn every gap into a traced task. Repeat with /dixi.build until nothing is missing.

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

Invocation

Argument: [feature slug]. 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 the feature spec and its acceptance criteria, its contracts, plan, 05-features/<slug>/tasks.md, the related tests and 00-governance/principles.md. Run the project's real tests through make verify when they exist and report the result; never claim a check ran when it did not.
  2. Read the code in the authorized roots named by the plan. For each criterion, contract clause and principle, decide whether the code meets it, citing file and line.
  3. Classify each gap with one type: missing (required, not implemented), partial (implemented without all its criteria), contradicts (the code does something the spec or a principle forbids) or unrequested (code with no spec behind it, to be specified or removed by a person). A conflict with a principle is always the highest severity.
  4. Append a ## Convergence YYYY-MM-DD section to 05-features/<slug>/tasks.md with one task per gap, continuing the numbering (T-NNN): type, the source it traces to (criterion, contract clause or principle ID), the evidence (file and line), the test to write first, and a risk level.
  5. If there are no gaps, leave tasks.md unchanged and answer that the feature has converged, with the evidence.
  6. Suggest /dixi.build for the first convergence task, or /dixi.clarify when a gap comes from an ambiguous spec.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

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

Next step