Claude Code Plugins

Community-maintained marketplace

Feedback

Manage backlog items across multiple backends (files, GitHub Issues, Linear). Configure your preferred task system in project CLAUDE.md.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name backlog-manager
description Manage backlog items across multiple backends (files, GitHub Issues, Linear). Configure your preferred task system in project CLAUDE.md.

Backlog Manager Skill

Overview

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
Files Local markdown in docs/todos/ Solo developers, simple projects
GitHub gh CLI Teams using GitHub Issues
Linear MCP server Teams using Linear
Beads bd CLI Dependency-aware workflows, AI agents

Configuration

Configure your preferred backend in your project's CLAUDE.md:

## Task Management

backend: files  # Options: files, github, linear, beads

# GitHub configuration (when backend: github)
# github_labels: ["backlog"]
# github_assignee: "@me"

# Linear configuration (when backend: linear)
# linear_team_id: TEAM-123
# linear_project_id: PROJECT-456

# Beads configuration (when backend: beads)
# beads_prefix: myapp               # Optional: custom issue prefix

Default: If no configuration is found, uses file-based backend.

When to Use This Skill

Create a backlog item when:

  • Work requires more than 15-20 minutes
  • Needs research, planning, or multiple approaches considered
  • Has dependencies on other work
  • Requires approval or prioritization
  • Part of larger feature or refactor
  • Technical debt needing documentation

Act immediately instead when:

  • Issue is trivial (< 15 minutes)
  • Complete context available now
  • No planning needed
  • User explicitly requests immediate action
  • Simple bug fix with obvious solution

Core Concepts

Status Lifecycle

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 Levels

Priority Meaning
p1 Critical - blocks other work or users
p2 Important - should be done soon
p3 Nice-to-have - can wait

Core Operations

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

Backend Selection

When this skill is invoked:

  1. Read configuration from project CLAUDE.md
  2. Load appropriate reference based on backend setting:
    • filesreferences/file-backend.md
    • githubreferences/github-backend.md
    • linearreferences/linear-backend.md
    • beadsreferences/beads-backend.md
  3. Follow backend-specific instructions for operations

Fallback Behavior

If the configured backend is unavailable:

  • GitHub unavailable (gh not authenticated): Fall back to files
  • Linear unavailable (MCP not configured): Fall back to files
  • Beads unavailable (bd not installed or not initialized): Fall back to files
  • Warn user about the fallback

Integration with Development Workflows

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

Key Distinctions

Backlog manager (this skill):

  • Persisted tracking across sessions
  • Multiple backend options
  • Team collaboration
  • Project/sprint planning

TodoWrite tool:

  • In-memory task tracking during single session
  • Temporary progress tracking
  • Not persisted to disk
  • Different purpose from backlog management