DIXI Spec Kit documentation Español · Source on GitHub

/dixi.tasks

Purpose

Split a plan into tasks with criteria, dependencies and risk level.

Turn the plan for the feature in $ARGUMENTS into small, ordered tasks linked to their specs.

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. Read the feature, its contract, its test plan and related ADRs. If a structural ADR is still "Proposed", flag it as a blocker.
  2. Write 05-features/<slug>/tasks.md with a task list. Each task has: ID (T-NNN), description, acceptance criterion it covers, dependencies, risk level (0 fix, 1 clear rules, 2 with doubts, 3 structural) and link to the spec.
  3. Order by dependencies; each task's tests are written before its code.
  4. A level 3 task needs the person's validation before /dixi.build.
  5. Suggest /dixi.build T-001 (or the first unblocked task).

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