DIXI Spec Kit documentation Español · Source on GitHub

/dixi.issues

Purpose

Turn a feature's tasks into GitHub issues with gh, after a preview the person confirms.

Publish the open tasks of the feature in $ARGUMENTS as GitHub issues, so the team can track them, without creating anything the person has not seen and confirmed.

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

Invocation

Argument: [feature slug]. 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 05-features/<slug>/tasks.md, the feature spec and 00-governance/principles.md. Select open tasks (T-NNN not marked done). Skip tasks already listed in 05-features/<slug>/issues.md.
  2. Check gh auth status and the target repository (gh repo view). If gh is missing or not authenticated, stop and tell the person how to authenticate; never ask for or handle a token.
  3. For each task, look for an existing issue with the same title (gh issue list --search). Show a preview table: task, title, body (task, criterion, dependencies, risk, links to the spec and tasks), labels, and whether an issue already exists.
  4. Ask the person to confirm the list. Create nothing until the answer is an explicit yes; the person may remove items.
  5. Create each confirmed issue with gh issue create, one at a time, and append its number and URL to 05-features/<slug>/issues.md. Stop at the first error and report what was created.
  6. Suggest /dixi.build for the first task.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: issues created with their URLs, tasks skipped and why, checks (run, failed, not run), open items and the suggested next command.

Next step