All commands

Command

/consolidate-issues

inventory → cross-check history → close → migrate → bundle

Triage the backlog against git history; keep what still matters.

See it run

Illustrative terminal recording of the stages /consolidate-issues runs, in order.
Illustrative — the stages /consolidate-issues runs, in order.

How to run it

Run it in your harness

/consolidate-issues [scope filter such as label/area] [apply] — no args: the whole open backlog, report-only

<angle brackets> = required · [square brackets] = optional

How it works

  1. Inventory

    List the open issues in scope.

    No specialist — the run lists the backlog.

  2. Evidence

    Match them against commits and merged PRs so a close has a reason.

    Still evidence-first, no spawn.

  3. Verdicts

    Close, keep, or rewrite each one. The product-manager owns every verdict.

  4. Bundle

    Group what remains into themes you can actually ship.

When to use

  • Open issues are stale, duplicated, or already shipped.
  • Starting from a brief? /plan-epics. Shipping survivors? /ship-issue.

The skill

The installer ships the full skill — stages, gates, config — from commands/consolidate-issues.md.

Read the skill on GitHub