skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
majesticlabs-dev/majestic-marketplace74 installs

backlog-manager

Manage backlog items across multiple backends (GitHub Issues, Linear, Beads). Configure task_management in .agents.yml.

How do I install this agent skill?

npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill backlog-manager
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubfail

    The backlog-manager skill presents a high security risk by instructing the agent to download and execute shell scripts directly from untrusted personal GitHub repositories using the curl | bash pattern. Additionally, the skill processes external backlog data from various backends, creating a surface for indirect prompt injection as this data is subsequently used in shell commands and filesystem operations without evident sanitization.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 2 issues

  • Runlayerwarn

    7/7 files flagged

What does this agent skill do?

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:

BackendIntegrationBest For
GitHubgh CLITeams using GitHub Issues
LinearMCP serverTeams using Linear
Beadsbd CLIDependency-aware workflows, AI agents

For simple/solo projects: Use native Tasks (TaskCreate, TaskList, TaskUpdate) instead of backlog-manager.

Configuration

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.

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
StatusMeaning
pendingNeeds triage/approval before work begins
readyApproved and ready for implementation
completeWork finished, acceptance criteria met

Priority Levels

PriorityMeaning
p1Critical - blocks other work or users
p2Important - should be done soon
p3Nice-to-have - can wait

Core Operations

Each backend implements these operations:

OperationPurpose
CREATEAdd new backlog item
LISTQuery existing items
UPDATEModify item (status, priority, details)
COMPLETEMark 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:
    • github → references/github-backend.md
    • linear → references/linear-backend.md
    • beads → references/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 native Tasks
  • Linear unavailable (MCP not configured): Fall back to native Tasks
  • Beads unavailable (bd not installed or not initialized): Fall back to native Tasks
  • Warn user about the fallback

Integration with Development Workflows

TriggerFlow
Code review findingsReview → Create items → Triage → Work
PR commentsResolve PR → Create items for complex fixes
Planning sessionsBrainstorm → Create items → Prioritize → Work
Technical debtDocument → Create item → Schedule
Feature requestsAnalyze → Create item → Prioritize

Key Distinctions

Backlog manager (this skill):

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

Native Tasks (TaskCreate, TaskList, TaskUpdate):

  • Session task tracking with file persistence (~/.claude/tasks/)
  • Supports dependencies (blockedBy, blocks)
  • Can be shared across sessions via CLAUDE_CODE_TASK_LIST_ID env var
  • Use for: in-session progress tracking, subagent coordination, simple task lists
  • Different from backlog manager: Tasks are ephemeral coordination, backlog is project planning

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/majesticlabs-dev/majestic-marketplace/backlog-manager">View backlog-manager on skillZs</a>