DIXI Spec Kit documentation Español · Source on GitHub

/dixi.plan

Purpose

Plan contracts, decisions, risks and tests for a feature.

Produce the technical plan for the feature given in $ARGUMENTS: affected contracts, proposed ADRs, risks and verification path.

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

Invocation

Argument: <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 plan --target <FEATURE-ID> --request "<plan goal>" and follow its steps.
  2. Choose the stack with the person if it is not recorded in 00-master-spec.md yet; do not infer it.
  3. Depending on risk, also use dixi workflow prepare architecture, dixi workflow prepare contract and dixi workflow prepare threat-model on the same feature.
  4. Write or update the contract in 07-contracts/ and the test plan in 11-quality/, and register them in .dixi/traceability.json (kind: contract with the feature as parent; kind: test with the contract or feature as parent).
  5. Every structural decision goes in 09-architecture/adr/ADR-NNN-<slug>.md with status "Proposed"; it stays blocked until the person validates it.
  6. Suggest /dixi.tasks.

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

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