From majestic-engineer
Manages backlog items across GitHub Issues, Linear, and Beads backends via unified CREATE/LIST/UPDATE/COMPLETE operations. Configure task_management in .agents.yml for team workflows with dependencies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-engineer:backlog-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The backlog manager provides a unified interface for tracking work items across different task management systems. Choose your backend based on team preferences and existing tooling.
The backlog manager provides a unified interface for tracking work items across different task management systems. Choose your backend based on team preferences and existing tooling.
Supported Backends:
| Backend | Integration | Best For |
|---|---|---|
| GitHub | gh CLI | Teams using GitHub Issues |
| Linear | MCP server | Teams using Linear |
| Beads | bd CLI | Dependency-aware workflows, AI agents |
For simple/solo projects: Use native Tasks (TaskCreate, TaskList, TaskUpdate) instead of backlog-manager.
Configure your preferred backend in your project's .agents.yml:
task_management: github # Options: github, linear, beads
# Workflow labels (for github/linear backends)
workflow_labels:
- backlog
- in-progress
- ready-for-review
- done
# Beads configuration (when task_management: beads)
# beads_prefix: myapp # Optional: custom issue prefix
Default: If no configuration is found, use native Tasks (TaskCreate, TaskList, TaskUpdate) for simple tracking.
Create a backlog item when:
Act immediately instead when:
All backends follow this status workflow:
pending → ready → complete
| Status | Meaning |
|---|---|
| pending | Needs triage/approval before work begins |
| ready | Approved and ready for implementation |
| complete | Work finished, acceptance criteria met |
| Priority | Meaning |
|---|---|
| p1 | Critical - blocks other work or users |
| p2 | Important - should be done soon |
| p3 | Nice-to-have - can wait |
Each backend implements these operations:
| Operation | Purpose |
|---|---|
| CREATE | Add new backlog item |
| LIST | Query existing items |
| UPDATE | Modify item (status, priority, details) |
| COMPLETE | Mark item as done |
When this skill is invoked:
backend setting:
github → references/github-backend.mdlinear → references/linear-backend.mdbeads → references/beads-backend.mdIf the configured backend is unavailable:
| Trigger | Flow |
|---|---|
| Code review findings | Review → Create items → Triage → Work |
| PR comments | Resolve PR → Create items for complex fixes |
| Planning sessions | Brainstorm → Create items → Prioritize → Work |
| Technical debt | Document → Create item → Schedule |
| Feature requests | Analyze → Create item → Prioritize |
Backlog manager (this skill):
Native Tasks (TaskCreate, TaskList, TaskUpdate):
~/.claude/tasks/)blockedBy, blocks)CLAUDE_CODE_TASK_LIST_ID env varnpx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineerManages backlog items synced to GitHub Issues via MCP tools. Create, list, view, update, close, resolve, groom, and sync without direct file edits.
Decomposes GitHub issues into structured Beads epics, tasks, and sub-tasks with objectively verifiable acceptance criteria and dependencies. Useful for planning actionable work in Beads projects.
Implements external backlog integration with GitHub Issues, Linear, or Jira. Bridges local documents with external issue status and priority. Configured via stack.md.