backlog · sammcj — Claude Code skill: what it does, how to install
Tracks bugs and features in local Markdown files or GitHub Issues. Keeps backlogs tidy without drafting heavy PRDs or specifications.
Apache-2.0 ★ 173 updated 2026-10-30
npx skills add sammcj/agentic-coding --skill backlog -a claude-codeWhat backlog does
The skill routes backlog items automatically. It checks for BACKLOG.md or docs/BACKLOG.md first. When found, it writes local entries with category prefixes like [bug] or creates numbered files matching 0001-slug.md. If no file exists in an original repository, it defaults to GitHub Issues.
Duplicate checks run before creating any entry via grep or gh issue list --search. Items fall into four fixed buckets: bug, enhancement, chore, and documentation. During reviews, open items appear ordered from oldest to newest, allowing you to triage stale records, cluster themes, or pick a ticket to start working.
GitHub integration relies on an authenticated gh CLI. If you need full product specs or PRD authoring, this tool will not generate them.
What it helps with
- file bugs and feature requests directly into the backlog
- search existing issues for duplicates before filing
- triage stale tickets and confirm closing them
- cluster open backlog tasks into common themes
Example prompts for the agent
- Add a bug to the backlog: user avatar fails to render on Safari
- Review the backlog and show open items by category
- Triage open tasks and merge duplicate issues
How to install backlog
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill backlog -a claude-code2Manually: put the files in place
~/.claude/skills/backlog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/backlog/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill backlog -a codex2Manually: put the files in place
.agents/skills/backlog/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill backlog -a cursor2Manually: put the files in place
.cursor/skills/backlog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sammcj/agentic-coding Skills/backlog/SKILL.md2Manually: put the files in place
.github/skills/backlog/SKILL.md1Skills CLI (Vercel)
npx skills add sammcj/agentic-coding --skill backlog -a gemini-cli2Platform CLI
gemini skills install https://github.com/sammcj/agentic-coding --path Skills/backlogManually: put the files in place
.devin/skills/backlog/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about backlog
How to install backlog in Claude Code?
Run npx skills add sammcj/agentic-coding --skill backlog -a claude-code in your terminal or place the file into ~/.claude/skills/backlog/SKILL.md.
Where does the backlog skill save items?
It targets BACKLOG.md or docs/BACKLOG.md first. For personal non-fork repositories without local files, it creates GitHub Issues instead.
Can I use this skill to write PRDs?
No. The skill is strictly scoped to quick bug entries, chores, enhancements, and backlog triage rather than full specifications.
Source text
SKILL.md · Apache-2.0
--- name: backlog description: Use when the user wants to add a bug or feature to the backlog, or list or triage the backlog. Not for PRDs or specs. --- # Backlog ## Destination First match wins: 1. `BACKLOG.md` or `docs/BACKLOG.md` -> local file. 2. The user's own repo, not a fork -> GitHub. 3. Otherwise ask. Create no backlog file unless the user picks one. Categories: `bug`, `enhancement`, `chore` (refactor, dependencies, CI, build, tests), `documentation`. Local: - Category as a title prefix, e.g. `[bug]`. Find dupes with grep. - Add a section, or a new file continuing the existing numbering (`0001-slug.md`). GitHub: - Category is an existing label (`gh label list`). Ask before creating one. - Dupes: `gh issue list --search "<keywords>"`. List: `gh issue list --limit 50 --json number,title,labels,createdAt`. - Add: write the body to a file in a `mktemp -d` directory, then `gh issue create --body-file <file>`. ## Add 1. Search for dupes first. On a near match, ask: update it or file new. 2. Guess the category. Ask at most one question in total, only when scope or category is ambiguous. 3. File it. Reply with the URL or path only. ## Review 1. List open items, grouped by category, oldest first: number, title, age. 2. Offer, letting the user choose: - **Triage**: relabel, close stale items, merge dupes. Confirm each close. - **Pick one**: load the item and stop. If `openspec/` exists, end with `Next: /opsx:propose from #<n>`. - **Themes**: cluster related items, suggest groupings. ## Notes - Keep the contents concise, quick and easy to read. - Use the users wording, if you have context you may add it, if clarification is required: ask, do not make up requirements.
© sammcj · Apache-2.0 · sammcj/agentic-coding
Similar skills
All skills for Git and GitHub →backlog by other authors comes first.