DIXI Spec Kit documentation Español · Source on GitHub

/dixi.specify

Purpose

Specify domain, module and feature with verifiable criteria.

Write the story and feature for $ARGUMENTS with rules, observable criteria and links to domain and module.

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

Invocation

Argument: <feature to specify>. 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 which feature to specify and stop.
  2. Pick the parent module (kind: module) in .dixi/traceability.json; if none fits, propose a domain and module and ask for confirmation. Run dixi workflow prepare specify --target <ID> --request "<summary>" and follow its steps.
  3. Create or update 05-features/<slug>/feature-spec.md with: story (As / I want / So that), numbered acceptance criteria verifiable from outside, business rules and assumptions marked as such.
  4. Register the feature in .dixi/traceability.json with a new ID (FEATURE-NNN), kind: feature, its path and the module as parent.
  5. Link the feature to its module and back.
  6. Suggest /dixi.clarify if doubts remain, otherwise /dixi.plan.

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