DIXI Spec Kit documentation Español · Source on GitHub

/dixi.quality

Purpose

Define the test strategy, quality budgets and verification matrix.

Define how the scope in $ARGUMENTS (or the whole project) is verified: test levels, budgets and a criterion-to-test matrix.

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

Invocation

Argument: [feature ID or scope]. 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. Read the features, contracts and the current make verify.
  2. Write or update 11-quality/strategy.md: test pyramid, tools per level, what make verify must run, and budgets (coverage floor, performance, accessibility and i18n checks when in scope).
  3. Write 11-quality/matrix.md mapping each acceptance criterion to its tests, marking criteria without tests.
  4. Never lower an existing budget or gate to make work pass; propose the change and let the person decide.
  5. Suggest /dixi.tasks for the missing tests.

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