DIXI Spec Kit documentation Español · Source on GitHub

/dixi.clarify

Purpose

Resolve doubts in a spec with questions and record decisions and assumptions.

Reduce ambiguity in the spec given in $ARGUMENTS by asking the person, and record their answers without mixing them with assumptions.

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

Invocation

Argument: <spec ID or path>. 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. Identify the spec by ID or path; if unclear, ask and stop.
  2. Run dixi workflow prepare clarify --target <ID> --request "<what to clarify>" and follow its steps.
  3. Find open questions, unverifiable criteria and contradictions. Ask at most five questions per round, most blocking first.
  4. Record each answer in the spec as "Decision (person, date)". Anything unanswered stays as "Assumption" or "Pending", never as a decision.
  5. Suggest another round if blocking 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