backlog-manager

Backlog manager unifies backlog items across multiple backends—GitHub, Linear, Files, and Beads—letting you create, list, update, and complete tasks through a single interface. Configure your preferred backend in .agents.yml and manage all items without switching tools.

Yes. The backlog manager supports backend-specific configuration and fallback logic, so the same CREATE, LIST, UPDATE, and COMPLETE operations work across File, GitHub, Linear, and Beads backends. Switch backends by updating .agents.yml without changing your workflow.

Fallback logic ensures progress continues when a backend is temporarily unavailable. The backlog manager automatically routes operations to configured fallback backends, maintaining access to your items across team workflows.

Backlog items enforce a status lifecycle (pending → ready → complete) and three priority levels (p1, p2, p3). Use these to triage tasks, align team priorities, and track progress across your development workflow.

Configure task_management settings in .agents.yml with your backend choice and credentials, then select your primary backend. The backlog manager handles the rest—no additional setup needed to begin creating and managing items.

Yes. The backlog manager integrates with development workflows including PR reviews and planning sessions. Reference backlog items across GitHub, Linear, and other backends to connect planning, task tracking, and code review.