DIXI Spec Kit documentation Español · Source on GitHub

/dixi.build

Purpose

Build a task test-first: red, green and verification.

Implement the task in $ARGUMENTS with TDD: failing tests, minimal code to green and make verify.

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

Invocation

Argument: <task 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. Find the task in 05-features/*/tasks.md. If a file in 05-features/<slug>/checklists/ has open items (- [ ]), list them and stop until the person closes them or decides to continue. If it does not exist, has open dependencies or is an unvalidated level 3 task, stop and say so. Read wip_limit in AGENTS.md (default 3); if gh is available and authenticated and the person already has that many open pull requests, stop and suggest finishing one first.
  2. Write the tests for the task's criterion first, in the project's language. Run them and show they fail for the expected reason. No failing test, no code.
  3. Propose recording the failing tests in their own commit, without Signed-off-by; the person signs later. From then on they are frozen tests.
  4. Write the minimal code to reach green. Do not change frozen tests; if you think one is wrong, stop and explain.
  5. Run make verify and show the real result. If it fails, fix the code, not the test.
  6. Register the tests in .dixi/traceability.json (kind: test) and mark the task done only with make verify green.
  7. Suggest /dixi.verify.

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