DIXI Spec Kit documentation Español · Source on GitHub

/dixi.promote

Purpose

Review the requirements to move MODE to prod and list missing evidence.

Check whether the project is ready to change MODE from mvp to prod, for the person to decide.

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

Invocation

Argument: [optional note]. 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 MODE, 00-master-spec.md, quality, security, operations and data documents.
  2. Write docs/promotion/<date>-prod.md with a checklist: tests and budgets, threat model, data retention, runbooks and SLOs, release and rollback process, owners, and the evidence for each item.
  3. Mark every item without evidence as missing. Do not soften requirements.
  4. Never edit MODE yourself: only the person changes it after reviewing the checklist.
  5. Suggest the commands that close each gap (/dixi.quality, /dixi.threat-model, /dixi.operate, /dixi.data).

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