DIXI Spec Kit documentation Español · Source on GitHub

/dixi.status

Purpose

Show project status and a justified next step.

Summarize where the project stands, where the last session left off and what to do next, without modifying files. $ARGUMENTS may narrow the area.

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

Invocation

Argument: [optional area]. 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 doctor and dixi check and summarize their results.
  2. Read MODE, 00-master-spec.md, .dixi/traceability.json and 05-features/*/tasks.md if present.
  3. If .context/handoff.md exists, read it and report what the last session did, what it left open and the next step it named. If it does not exist, say so and go on.
  4. List the recent changes to the contracts with git log --oneline -10 -- 07-contracts/, so the person sees which agreements moved while they were away. Skip this step, and say so, when the project is not a Git repository.
  5. Count pending markers, "Proposed" ADRs, open or blocked tasks and features without tests, and list the open tasks by ID.
  6. Name the next command and why (for example /dixi.clarify if blocking questions exist or /dixi.build T-003 if a task is unblocked). Prefer the next step of the handoff when it still applies.
  7. Do not modify files, commit or push.

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