DIXI Spec Kit documentation Español · Source on GitHub

/dixi.checklist

Purpose

Write requirement-quality checklists for a feature (unit tests for the spec).

Check the quality of the requirements of the feature named in $ARGUMENTS, not of its implementation: are they complete, clear, consistent, measurable and traced? Write the result as a checklist a person ticks.

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

Invocation

Argument: [feature slug and domain, for example orders security]. 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 feature spec, its plan, contracts and test plan if they exist, the parent module and domain, and 00-governance/principles.md. If the feature or the domain to check (for example security, accessibility, i18n, data, API, performance) is not clear, ask up to three questions and stop.
  2. Write 05-features/<slug>/checklists/<domain>.md. Each item is an unchecked box with a stable ID and a question about the requirement, not the code: - [ ] CHK-001 Is the error response for an expired session specified? [Completeness, feature-spec §Criteria 3]. Classify each item (completeness, clarity, consistency, measurability, coverage, traceability) and cite the spec section or principle it comes from; write [Gap] when the requirement is missing.
  3. If the file already exists, keep every item and its state; append new items with the next free IDs. Never tick, untick, reword or delete an existing item.
  4. Do not answer the questions or change the spec here. Point each gap to the operation that closes it (/dixi.clarify, /dixi.specify, /dixi.contract or /dixi.plan).
  5. /dixi.build stops while a checklist of the feature has open items, unless the person decides to continue.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: files touched, items added and open gaps, checks (run, failed, not run), open items and the suggested next command.

Next step