DIXI Spec Kit documentation Español · Source on GitHub

/dixi.duediligence

Purpose

Produce a due-diligence report backed by project artifacts, with gaps.

Produce the due-diligence report requested in $ARGUMENTS from existing project artifacts.

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

Invocation

Argument: <type: investor, customer or audit>. 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. If the type (investor, customer, audit) is not given, ask and stop.
  2. Run dixi check and gather the relevant artifacts: specs, ADRs, tests and their results, security, data, operations and compliance documents.
  3. Write 28-due-diligence/<type>.md: findings per area, each with links to its evidence, and a gaps section.
  4. Every statement cites an artifact; anything without evidence goes to gaps, never presented as fact.
  5. Do not include secrets, personal data or customer information.

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

No fixed next operation; /dixi.status suggests one.