backlogd

Plugin backlogd from marketplace buildwithclaude in davepoon/buildwithclaude. Commands read from the repo's manifest — yesterday.

Skills (8)

• ac

  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 ve

• develop

  The method a backlogd developer follows to turn one shaped issue into a solution — consult /docs (the living spec), treat the issue's ## Acceptance Criteria as the binding static target, ship a thin vertical slice with tests where they earn their keep, and verify against the AC before reporting solv

• graph-navigation

  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-histor

• linear

  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.

• retro

  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:i

• reviewer

  The trust model behind backlogd's `backlogd:reviewer` subagent — fresh context, restricted tool grant, mandatory machine-verifiable check execution with cited evidence, judge/act split. Use when implementing or modifying `/backlogd:review`, the reviewer agent, or any caller that dispatches the revie

• scrum

  backlogd's operating model for Scrum — the framework backlogd interprets and runs on. Use whenever a backlogd agent needs to reason about Scrum primitives: the three accountabilities (Product Owner, Scrum Master, Developers), the five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Spri

• worktree-isolation

  backlogd's per-session worktree isolation pattern — one isolated git worktree per concurrent agent session, the identity guard armed before any commit, the lock/no-prune convention, and the dedicated-clone escalation when the native pattern proves insufficient. Loaded when a worktree or parallel ses

Slash commands (7)

• /backlogd:init

  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.

• /backlogd:release

  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.

• /backlogd:retro

  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 P

• /backlogd:review

  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.

• /backlogd:scope

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

• /backlogd:solve

  Execute a shaped Linear problem — dispatch a developer per unit of work in dependency order, record each result, and on the happy path auto-chain the independent verdict review and merge a fully-green increment to Done with no human gate (ship-on-green, on by default). Routes ops-only problems (kind

• /backlogd:status

  Scrum-master standup — survey the active problems in Linear, report progress + blockers to the product owner, and refresh a rolling-7-day forecast onto the engagement Project's description.

Subagents (4)

• developer

  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.

• refiner

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

• reviewer

  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

• tester

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

MCP servers (1)

• linear

  connects to: https://mcp.linear.app/mcp

Hooks (2)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/check-git-identity.sh"

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/session-bootstrap.sh"

Similar plugins