backloglisted

# Backlog The backlog is the **work-intake home** — latent work intent captured as `issue`, `improvement`, `chore`, `risk`, or `idea` items, triaged and promoted into slices. `needs` = hard dependency. `after` = soft ordering (suggestion). The CLI is the source of truth for exact flags: `doctrine backlog --help` ## Creating new backlog items: - [ ] Determine kind membership / validity - [ ] Survey backlog for potential duplicates / neighbors - [ ] Prefer expanding / improving an appropriate existing item - [ ] Choose a clear, concise title - [ ] Create the new backlog item - [ ] Read & fill its template - [ ] Tag it appropriately and consistently - [ ] Record any dependencies and appropriate sequencing priorities ## Verbs | intent | verb | |---|---| | capture a new item | `doctrine backlog new <kind> [title]` | | survey items | `doctrine backlog list [--kind …] [--status …] [--tag …] [--all]` | | inspect one item | `doctrine backlog show <ID>` | | transition status | `doctrine backlog edit <ID> --status <STATUS> [--resolution <R>]` | | add/remove tags | `doctrine backlog tag <ID> <tag> … [--remove <tag>]` (adds positional; `--remove`/`-d` repeatable) | | record a hard dep | `doctrine backlog needs <ID> <DEP-ID> [<DEP-ID> …]` | | record soft ordering | `doctrine backlog after <ID> <PREDECESSOR-ID>` | ## Kind membership - **issue** — a bug or defect - **improvement** — a tooling/UX gap or enhancement (no new feature) - **chore** — housekeeping, tech-debt, refactor