DIXI Spec Kit documentation Español · Source on GitHub

/dixi.threat-model

Purpose

Model STRIDE threats with mitigations and planned tests.

Identify threats for the target in $ARGUMENTS and attach a mitigation and a planned test to each one.

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

Invocation

Argument: <module or 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. Run dixi workflow prepare threat-model --target <ID> --request "<scope>" and follow its steps.
  2. Identify assets, trust boundaries and untrusted inputs from the specs and contracts.
  3. Write 13-security/<slug>-threat-model.md with a STRIDE table: threat, mitigation, planned test and residual risk.
  4. A threat without mitigation stays an open risk and blocks /dixi.build of the affected work until the person decides.
  5. Do not run penetration tests or access external systems.
  6. Suggest /dixi.plan or /dixi.tasks.

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