backlog

Manage GitHub backlog issues and synchronize local planning artifacts.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/sakebomb/scaffold --skill backlog-sakebomb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/sakebomb/scaffold/tree/main/.claude/skills/backlog
Command: npx skills add https://github.com/sakebomb/scaffold --skill backlog-sakebomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the GitHub issues backlog. Bridge between GitHub Issues and local task management.

Core Features & Use Cases

  • Show open issues, group by priority labels (P0-critical, P1-high, P2-medium, P3-low, or unlabeled), and present a concise backlog summary.
  • Create new GitHub issues interactively with Title, Type (bug/feature/task), Priority (P0-P3), Description, and Acceptance criteria.
  • Pick an issue to start work: create a branch, add in-progress label, move from ready to in-progress, and write the plan to tasks/todo.md.
  • Close issues when work is completed and document a brief summary.

Quick Start

Run the backlog workflow on a GitHub repository to view, create, or pick issues and synchronize with your local plan.

Frequently Asked Questions about backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage my GitHub issues backlog and sync it with local task planning?

Managing a GitHub issues backlog is automated by connecting GitHub Issues to local artifacts, allowing you to view, create, pick, and close issues while synchronizing plans directly to your local task files.

Can I create a GitHub issue branch and update my local plan automatically?

Yes, picking a GitHub issue automatically creates a working branch, adds an in-progress label, and writes the issue plan to a local tasks/todo.md file to bridge remote tracking with local development.

How do I automatically group and prioritize GitHub issues by labels?

Viewing open GitHub issues groups them by priority labels like P0-critical, P1-high, P2-medium, and P3-low, presenting a concise backlog summary so teams can easily maintain a prioritized queue.

Do I need the gh CLI installed to automate GitHub backlog workflows?

Yes, automating GitHub backlog management requires gh CLI access to interact with GitHub Issues, ensuring the Skill can fetch, create, and update issue states directly from your repository.

What is the best way to close GitHub issues and document work summaries?

Closing GitHub issues through this workflow completes the task and automatically documents a brief summary, maintaining a clear record of resolved work within your GitHub repository backlog.