backlog

Convert rough bug lists into standalone task files through structured user interviews.

1|Updated Dec 18, 2009
One-click install
npx skills add https://github.com/thurn/dotfiles --skill backlog-thurn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/thurn/dotfiles/tree/main/.llms/skills/backlog
Command: npx skills add https://github.com/thurn/dotfiles --skill backlog-thurn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A one-line bug report is rarely an actionable task. This Skill turns a loose bullet-point list of 10-30 bugs or issues into detailed, standalone markdown task files in /tmp/backlog/ that a future implementer agent can pick up without any additional context. ## Core Features & Use Cases - Interview-driven clarification: Uses the grill-me interview pattern to uncover what is actually broken, why it matters, and what "fixed" looks like, instead of guessing from one-line descriptions. - Subsystem clustering and interleaved numbering: Groups tasks by subsystem and round-robin assigns task numbers so parallel implementation minimizes merge conflicts. - Standardized task template with universal instructions: Writes per-task files with Problem, Acceptance criteria, and Implementation notes sections, then appends universal QA and implementation guidance via an idempotent shell script. - Use Case: Paste a raw list of 15 bug reports from your issue tracker and receive 15 self-contained task files in /tmp/backlog/, each ready for an autonomous implementer agent. ## Quick Start Ask the agent to groom this backlog list of bugs into standalone task files using the backlog skill.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I turn a rough bug list into actionable tasks?▼

Provide a bullet-point list of 10-30 issues and the skill interviews you about each item, then writes one standalone markdown task file per bug into /tmp/backlog/. Each file describes the problem, expected behavior, and task-specific acceptance criteria.

How does backlog grooming work with an AI agent?▼

The agent interviews you one question at a time to understand what is broken, why it matters, and what fixed looks like. It deliberately avoids writing reproduction steps or code pointers, since the implementer agent handles those itself.

Why are task numbers not assigned in input order?▼

Tasks are clustered by subsystem and numbered via round-robin interleaving so adjacent tasks touch different subsystems. This minimizes merge conflicts when multiple tasks are implemented in parallel, and a bullet-to-task mapping is reported back.

What happens if my bug list has fewer than 10 items?▼

The skill is sized for 10-30 items and will ask for confirmation before proceeding with a shorter or longer list. You can still proceed, but the workflow is optimized for that range.

What does the append-general-instructions script do?▼

The script appends a universal How to Implement This Task section to every task file, covering standard acceptance criteria, QA blocker policy, and UX expectations. It is idempotent, skipping files that already contain the section.