backlogd

One-time Linear workspace bootstrap — bring the team into backlogd's canonical shape (labels · workflow states · templates) by driving the local config engine. Opt-in, setup-only, key-free in the orchestrator; the engine reads the Admin key itself. Pass --dryrun to print the plan and touch nothing.

Cut a release — promote the integration branch to the release branch, bump the plugin version on a release branch, merge with a merge commit, tag vX.Y.Z, and back-merge so the two branches re-sync.

Sprint Retrospective — over a completed milestone (or a cycle / date / count fallback), read the execution graph + what happened, detect cross-issue patterns, classify the load-bearing learnings, and file them as candidate `kind:improvement` issues for the PO to prioritize. The retro proposes; the PO prioritizes.

Quality gate — dispatch an independent reviewer subagent against a solved problem's acceptance criteria, then act on its verdict — accept to Done, send back to In Progress, or escalate a judgement call. The reviewer judges; the orchestrator acts.

Shape a Linear problem into an executable, decomposed issue — write acceptance criteria, decompose into sub-issues, sequence with blocked-by — then stop. No solving.

Owns the solution to one backlogd problem. Dispatched by /backlogd:solve with a single problem to solve; takes a concrete action, writes its progress to its own Linear issue, and reports the outcome.

drafts AC + decomposition for one backlogd problem; dispatched by /backlogd:scope and /backlogd:solve triage

Owns the verdict on a backlogd unit or solved problem. Dispatched in one of two modes — `pre-commit-gate` (gates a unit's diff before commit, inside /backlogd:solve) or `verdict` (drafts the user-facing AC + DoD verdict for an In-Review problem, inside /backlogd:review). Reads its issue + diff with a fresh context, runs every machine-verifiable check itself with cited evidence, and returns its judgement for the scrum-master to act on. Read-only filesystem, no state transitions, no code changes.

writes/expands tests proving the AC of one backlogd unit; dispatched by /backlogd:solve after developer

backlogd's contract for typed Acceptance Criteria — every `## Acceptance Criteria` item declares *how it is verifiable* via an optional `[test]` / `[manual]` / `[review]` prefix tag; untagged items default to `[review]` (backwards compatible). Load when shaping AC (`/backlogd:scope`) or judging a verdict (`/backlogd:review`).

The method a backlogd developer follows to turn one shaped issue into a solution — consult /docs (the living spec), treat the issue's

Query backlogd's local agent-execution + memory graph (.backlogd/graph/) — read-only. Records what only the loop knows (dispatch outcomes, latency, rework events) plus a low-signal aside of which files past problems touched. Use when a backlogd agent wants prior context before acting (problem-history / module-history / find-similar) or when a maintainer wants framework-effectiveness metrics (graph.py report). Local JSON only, no Linear/MCP — safe inside the developer's solve-only boundary. Pairs with references/graph-schema.md (nodes/edges/IDs) and references/graph-queries.md (copy-paste recipes).

backlogd's operating model for Linear via the official MCP. Use whenever a backlogd agent touches Linear — picking up a problem, deciding Issue-vs-Project structure, decomposing work into sub-issues, setting blocks/blocked-by, transitioning workflow state, reporting progress, or surfacing blockers. Pairs with references/linear-mcp.md (exact mcp__linear__* usage) and references/linear-model.md (Linear object model + terminology).

backlogd's Sprint Retrospective mechanism — over a completed milestone (or a cycle / date / count fallback) the retro reads the execution graph as objective evidence, detects cross-issue patterns no single review can see, classifies each learning, and files the load-bearing ones as candidate `kind:improvement` issues for the PO to prioritize. The retro proposes; the PO prioritizes. Use when implementing or modifying `/backlogd:retro`, or any caller that runs the read → detect → classify → file pipeline.

2 hooks across 1 event

Constrains agent-authored Markdown so it renders cleanly on Linear (language-tagged fences, no tables, no em-dashes, no status emoji, shallow nesting). The canonical rule-set for every backlogd agent-authored Linear comment, the developer, reviewer, tester, and scrum-master surfaces alike.