backloglisted

# Backlog Manage the project backlog — plan, track, and navigate work across phases, milestones, and epics. Natural language is the primary interface; these commands are shortcuts for complex operations. ## When to use When explicitly managing the backlog: planning phases, viewing roadmaps, restructuring work. Daily task interaction happens through natural language guided by the task-convention rule — no skill invocation needed. ## CLI Integration — MANDATORY **NEVER read or write tasks.json directly.** **Prefer MCP tools** (brana server) when available — structured JSON, 65% fewer tokens: ### Initiative Model (v3) **Epics are hierarchy nodes, not a field** (ADR-065). An epic is a top-level task with `type: "epic"` whose `subject` is the epic slug (e.g. `"cc-alignment"`). A task belongs to an epic through its `parent` chain — its nearest `type: "epic"` ancestor (walk helper: [`../_shared/epic-ancestor-walk.md`](../_shared/epic-ancestor-walk.md)). > **Retired — flat `epic` field.** The pre-v3 flat `epic` string field is gone and its set/add write paths are sealed (t-2310): `backlog_set(field: "epic")` and `brana backlog set <id> epic <slug>` are hard-rejected with `unknown field: epic`, and `brana backlog add --epic` is a warned no-op. Never set or create the field. Epic membership is written by setting `parent` to an epic node's id. > > **Mid-migration caveat (t-2698):** the ADR-065 backfill (promote old epic slugs to nodes, re-parent tasks) has only run in some proj