backlog
Skill1 starsChanged 3 months agoMITView on GitHub
Capture and rank a per-project backlog of work you want an agent to do unattended later. Use inside a project repo when you say "backlog this", "add to the backlog", "queue this for later", "have the runner do this", or when giving feedback about what automated work this project needs next. Also for reranking or dropping items.
39 other projects use a version of this.
Adopted by
Most recently taken up by
- Alter-ai/skill-labtheir own version, first seen Nov 15, 2026
- pronvis/skillstheir own version, first seen Nov 15, 2026
- gutohuida/AgentWeavetheir own version, first seen Nov 15, 2026
- newkayak12/claude-skillstheir own version, first seen Nov 1, 2026
- a-lottes/aSPARKtheir own version, first seen Nov 1, 2026
- ellebelle99/backlog-skilltheir own version, first seen Nov 1, 2026
Used with
Projects with it also use issue, worktree and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillissue
Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.
Also in 3 projects that use this
MicrosoftSkillworktree
Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 4 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 39
- nschurmann/hola-ai★ 253same name
- sammcj/agentic-coding★ 169same name
- camtrik/agent-trail★ 45same name
- a-lottes/aSPARK★ 25same name
- ovargas/virtual-team★ 14same name
- greglas75/zuvo★ 7same name
- gonimar/claude-web-studio★ 4same name
- gutohuida/AgentWeave★ 4same name
- maxekman/skills★ 4same name
- cirne/agent-skills★ 3same name
29 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- burndownSkill
- zettelkastenSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
If a verify is not inferable and they are clearly mid-flow, mark the item needs-shaping and move on.
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
backlog
Capture is cheap. Execution is expensive. This skill is the cheap half.
It maintains .claude/backlog.md in whatever repo you are standing in: a ranked
list of work you want done unattended, in your words, captured fast enough that
you do not lose your train of thought. The burndown skill drains it later.
The backlog is unbounded. Put everything in it. The execution queue that burndown builds is capped at 3 to 5 items. That asymmetry is the whole design: capturing an idea should cost nothing, and committing to do one should cost something.
Capture mode (the default)
- Take the feedback as given. One item, a rapid-fire list, or a vague
direction. Record each one near-verbatim in its
ask:line, dated. Do not improve their wording; you will want to know what they actually said. - Shape each item toward the gate below. Infer
do,verify,boundsandsizefrom the repo, and propose them. Confirm in one batch at the end, never one question per item. Interrogating someone mid-capture is how you train them to stop capturing. - If a
verifyis not inferable and they are clearly mid-flow, mark the itemneeds-shapingand move on. Shape it later. - An item that can never run unattended gets
needs-humanand one line of why. It stays visible; burndown will never take it. - Rank where they say. Unstated means bottom. On a rerank or drop, edit in place and keep dropped items with their reason.
The autonomy gate
An item is only ready if all four are true. This is the same gate burndown
re-checks before it runs anything, and it is the reason the whole thing is safe
to leave alone.
- No judgment call. Taste, naming, product decisions, anything where you would want a say. If a reasonable person could do it two ways and you would care which, it is not ready.
- Reversible. The worst outcome is fixed by
git restoreorgit revert. - Has a programmatic verify. A command that exits non-zero on failure. Not "check that it looks right". If you cannot name the command, you do not yet know what done means.
- Bounded. Named paths the work stays inside.
Never queue, regardless of how it is written up: anything needing credentials or secrets, anything that sends outward (email, posts, messages, deploys, pushes), anything touching money, and anything inside a path you have marked protected.
File format
# Backlog: <repo name>
Feeder for burndown. Drained top-down; higher = sooner.
## B1: <imperative title> [ready]
- added: 2026-08-07 ask: "<your words, near-verbatim>"
- do: <steps, with a stated default for every decision>
- verify: `<command>` (timeout 600s); pass = <observable outcome>
- bounds: <paths this may touch>
- size: S | M | LStatuses: ready (promotable), needs-shaping (captured fast, shape later),
needs-human (fails the gate by nature), promoted (moved into the queue;
keep the date), dropped (with a reason). B-numbers are never reused, so a
reference in a commit message stays meaningful forever.
Sizes are time caps, not estimates: S 15 min, M 45 min, L 90 min. Anything bigger is not one task.
Rules
- Never invent backlog items. This file holds only what you were actually asked for. An agent that pads its own to-do list is an agent nobody trusts.
- The most recent instruction wins on ordering. No silent reranking.
- A bare
ask:line withneeds-shapingis a valid entry. Never let shaping questions slow down a capture burst.
Setup
Drop this file at ~/.claude/skills/backlog/SKILL.md. Commit
.claude/backlog.md in each repo so the list survives a fresh clone.
Pairs with the burndown skill, which drains it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

