DIXI Spec Kit documentation Español · Source on GitHub

/dixi.interview

Purpose

Fill the project's pending slots through a guided interview, one question at a time.

Fill the {{pending: …}} slots in the project's documents by interviewing the person, one question at a time. $ARGUMENTS may narrow the interview to an area (for example 01-business) or a file.

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

Invocation

Argument: [optional area or file]. 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 placeholders to see which files still have pending slots and how many. If none remain, say so and stop.
  2. Read profile in .dixi/project.json to know which areas apply. Follow the order of the profile: start with 00-master-spec.md and 01-business/, then the remaining areas the profile installs. With $ARGUMENTS, cover only that area or file.
  3. For each slot, ask one question at a time, in plain language, with the context the person needs to answer. Offer an example or a default only as a suggestion, never as the answer.
  4. Write each answer in place of its marker, in the language of the document. Never answer for the person: if they do not know or prefer to leave it for later, keep the marker as is.
  5. Fill only slots. Do not edit rules, policies or text marked as norms; if an answer contradicts one, show the contradiction and ask.
  6. When an answer is a structural decision (stack, architecture, data storage, integrations), record it in 09-architecture/adr/ADR-NNN-<slug>.md with status "Proposed"; it stays blocked until the person validates it.
  7. At the end of each area, summarize what you wrote and ask whether to continue with the next one. Run dixi placeholders again to show what remains.
  8. Suggest /dixi.discover or /dixi.clarify if open questions remain, or /dixi.status.

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