DIXI Spec Kit documentation Español · Source on GitHub

/dixi.operate

Purpose

Define SLOs, observability, runbooks and incident preparation.

Prepare the operation of the service in $ARGUMENTS: SLOs, observability, runbooks and incident response.

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

Invocation

Argument: <service or component>. 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 architecture, contracts and threat model of the service.
  2. Write or update 15-operations/<service>.md: SLIs and SLOs, alerts, dashboards and logs (without personal data), dependencies and capacity assumptions.
  3. Write 15-operations/runbooks/<service>-<scenario>.md for each critical failure: detection, diagnosis, mitigation, rollback and communication.
  4. Do not run commands against production or any live environment; runbooks describe steps for people and pipelines.
  5. Suggest /dixi.promote when operations are ready.

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