backlog

Organizes GitHub issue backlog via triage, fix-one, and drain modes.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dmooney/Rundale --skill backlog-dmooney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/backlog
Command: npx skills add https://github.com/dmooney/Rundale --skill backlog-dmooney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents a messy GitHub issue backlog by turning un-triaged and bug-oriented work into consistent, labeled, end-to-end fixes that close out issues when done.

Core Features & Use Cases

  • Triage mode: Classifies open issues missing P-priority and/or theme labels using the project’s triage vocabulary, then applies the correct label set without conflicting old priorities.
  • Fix-one mode: Executes a single issue workflow end-to-end—diagnose, implement, test, verify with the project harness, and update docs—then commits the fix in the expected style.
  • Drain mode: Runs multi-wave parallel bug-fix sweeps that triage → dispatch fix agents → schedule wakeups → merge PRs as CI gates pass, closing issues as they go green.

Quick Start

Use backlog in triage mode by asking: "triage the backlog" so open issues are labeled by theme and P0–P3 according to docs/agent/triage-vocabulary.md.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I automate GitHub issue triage and apply priority labels?

Automate GitHub issue triage by classifying open issues missing P-priority and theme labels using a project's triage vocabulary, then applying the correct P0–P3 label set while stripping old priorities to prevent conflicts.

Can I fix a GitHub issue end-to-end including tests and documentation?

Yes, you can fix a GitHub issue end-to-end by diagnosing, implementing, testing, verifying with the project harness, updating docs, and committing the fix in the expected repository style.

What is the best way to drain a GitHub bug backlog using parallel pull requests?

The best way to drain a bug backlog is running multi-wave parallel bug-fix sweeps that triage, dispatch fix agents, schedule wakeups, and merge PRs as CI gates pass, closing issues automatically.

How does CI gating work when merging agent-generated pull requests?

CI gating for agent-generated pull requests works by scheduling wakeups for sweep-loop execution and gating merges on CI success and resolved bot threads before closing the referenced GitHub issues.

Do I need a triage vocabulary file to label GitHub issues by priority?

Yes, you need a triage vocabulary file like docs/agent/triage-vocabulary.md to classify open issues by theme and P0–P3 priority, preserving non-priority labels while stripping old P* priorities on re-triage.