DIXI Spec Kit documentation Español · Source on GitHub

/dixi.verify

Purpose

Run project verification and map criteria to tests.

Gather real verification evidence for the project or the feature in $ARGUMENTS, without modifying files.

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

Invocation

Argument: [feature ID]. 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 make verify and keep the output. Never report as green anything that was not run.
  2. For the given feature (or all), map each acceptance criterion to the tests that cover it, using .dixi/traceability.json and the test code.
  3. Flag criteria without tests, skipped or failing tests, and checks the project has not wired into make verify yet.
  4. Do not fix code here: propose /dixi.build for each gap.
  5. Suggest /dixi.review when everything is green.

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