backlogmd

l-lin's avatarfrom l-lin

Manage backlog tasks using the Backlog.md CLI. Use for creating, editing, viewing, and searching tasks in your backlog.

⭐14stars🔀1forks📁View on GitHub🕐Updated Jan 3, 2026⬇️2downloads

When & Why to Use This Skill

The Backlog.md CLI skill is a robust task management solution designed for developers and AI agents to manage project backlogs directly through a command-line interface. It streamlines the lifecycle of a task—from creation and requirement definition with acceptance criteria to implementation planning and status tracking—ensuring organized and searchable project documentation within a markdown-based workflow.

Use Cases

  • Agile Task Organization: Efficiently create and structure user stories or technical tasks with multi-line descriptions, subtasks, and specific acceptance criteria.
  • Development Workflow Integration: Update task statuses, assign owners, and set priorities (low/medium/high) without leaving the terminal or development environment.
  • Implementation Planning: Document detailed technical plans and progress notes directly within tasks to maintain a clear audit trail of development decisions.
  • Backlog Refinement & Search: Quickly locate specific tasks using keyword searches or filter the backlog by status, assignee, or priority to identify high-impact work items.
  • AI Agent Autonomy: Enables AI coding assistants to autonomously manage their own 'To Do' lists, check off completed requirements, and document their implementation steps for human review.
namebacklog.md
descriptionManage backlog tasks using the Backlog.md CLI. Use for creating, editing, viewing, and searching tasks in your backlog.

Backlog.md CLI Skill

You are a Backlog.md CLI expert assistant.

Task Management Commands

Create Task

backlog task create "Title" -d "Description" --ac "Criterion 1" --ac "Criterion 2"
  • Multiple --ac flags for acceptance criteria
  • Use --draft for draft tasks
  • Use -p <parent-id> for subtasks
  • Include JIRA ticket in title: "[PROJ-123] Task description"

View Task

backlog task 42 --plain
  • Always use --plain flag for AI-friendly output
  • Shows all task details, ACs, plan, notes

Edit Task Metadata

backlog task edit 42 -s "In Progress" -a @myself
backlog task edit 42 -t "New Title" -l backend,api --priority high
  • -s, --status - Change status ("To Do", "In Progress", "Done")
  • -a, --assignee - Assign to user
  • -t, --title - Update title
  • -l, --labels - Set labels (comma-separated)
  • --priority - Set priority (low/medium/high)

Manage Acceptance Criteria

# Add multiple ACs
backlog task edit 42 --ac "New criterion" --ac "Another one"

# Check ACs (mark complete)
backlog task edit 42 --check-ac 1 --check-ac 2

# Uncheck AC
backlog task edit 42 --uncheck-ac 3

# Remove AC
backlog task edit 42 --remove-ac 4

Add Implementation Content

# Add plan (use ANSI-C quoting for newlines)
backlog task edit 42 --plan $'1. Research\n2. Implement\n3. Test'

# Add notes (PR description)
backlog task edit 42 --notes $'Implemented X\nUpdated tests'

# Append to notes
backlog task edit 42 --append-notes $'- Fixed bug\n- Added validation'

Searching & Listing

Search Tasks

backlog search "keyword" --plain
backlog search "auth" --type task --status "To Do" --plain

List Tasks

backlog task list --plain
backlog task list -s "In Progress" -a @myself --plain
backlog task list --priority high --plain

Typical Implementation Workflow

# 1. Find work
backlog task list -s "To Do" --plain

# 2. Start work
backlog task edit 42 -s "In Progress" -a @myself

# 3. Add plan
backlog task edit 42 --plan $'1. Analyze\n2. Implement\n3. Test'

# 4. Mark ACs complete as you work
backlog task edit 42 --check-ac 1 --check-ac 2

# 5. Add implementation notes
backlog task edit 42 --notes $'Implemented using pattern X\nUpdated files Y and Z'

# 6. Mark done
backlog task edit 42 -s Done

Usage Guidelines

  1. Always use --plain flag when viewing/listing tasks for AI-readable output
  2. Never edit task files directly - Always use CLI commands
  3. Use ANSI-C quoting ($'...\n...') for multi-line content (plan, notes, description)
  4. Include JIRA ticket in title when applicable: [TICKET-123] Description
  5. Mark ACs complete as you work through them
  6. Start work properly: Set status "In Progress" and assign to yourself first

Error Handling

  • Check task exists: backlog task 42 --plain
  • List all tasks if ID unknown: backlog task list --plain
  • Use search for keywords: backlog search "topic" --plain
  • For AC operations, verify AC index with backlog task 42 --plain

Full help: backlog --help