DIXI Spec Kit documentation Español · Source on GitHub

/dixi.discover

Purpose

Discover the product vision, actors, scope and open questions.

Turn the idea described in $ARGUMENTS into vision, actors, scope, constraints and open questions, without inventing the person's decisions.

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

Invocation

Argument: <idea or need>. 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 for the idea and stop.
  2. Find the goal (kind: goal) in .dixi/traceability.json and run dixi workflow prepare discover --target <ID> --request "<short summary, no secrets>". Follow its steps and gates.
  3. Read AGENTS.md, 00-master-spec.md, MODE and 01-business/.
  4. Update 00-master-spec.md (problem, scope, out of scope, constraints) and 01-business/vision.md (goal, actors, success metrics). Keep existing IDs.
  5. Record each doubt as an open question in the spec, marked as pending; do not answer it yourself.
  6. Suggest /dixi.clarify if blocking questions remain, otherwise /dixi.specify.

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