Skip to content
Skills Library
Management & product · Planning

backlog

/backlog

Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug for X". Also use when the user wants to see what's open, triage stale items, or pick something to work on ("what's open?", "show me the issues", "review the backlog"). Auto-detects destination (GitHub via `gh` CLI, or local `docs/BACKLOG.md` / `docs/issues/`).

Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug for X". Also use when the user wants to see what's open, triage stale items, or pick something to work on ("what's open?", "show me the issues", "review the backlog"). Auto-detects destination (GitHub via `gh` CLI, or local `docs/BACKLOG.md` / `docs/issues/`).

Triggers from the description

create an issue for thatadd this to the backlogfile a quick bug for Xs open, triage stale items, or pick something to work on (s open?show me the issuesreview the backlog
Original author description

Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug for X". Also use when the user wants to see what's open, triage stale items, or pick something to work on ("what's open?", "show me the issues", "review the backlog"). Auto-detects destination (GitHub via `gh` CLI, or local `docs/BACKLOG.md` / `docs/issues/`).

How it works

  1. Destination detection
  2. Add mode
  3. Review mode
  4. Gotchas
Original SKILL.md headings · 62 lines, 750 words
SKILL.md preview
---
name: backlog
description: Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug for X". Also use when the user wants to see what's open, triage stale items, or pick something to work on ("what's open?", "show me the issues", "review the backlog"). Auto-detects destination (GitHub via `gh` CLI, or local `docs/BACKLOG.md` / `docs/issues/`).
disable-model-invocation: true
---

# Backlog management

Capture single items to a project backlog, or list and triage an existing one. Detect the user's intent and run in either **add** mode (one item being filed) or **review** mode (looking at what's there). The two modes share destination detection.

## Destination detection

Try in order; cache the result for any follow-up in the same flow:

1. `gh repo view` succeeds → use GitHub issues for that repo.
2. Else `docs/BACKLOG.md` exists → append for adds, read for reviews.
3. Else `docs/issues/` directory exists → per-issue files (one `.md` per issue, numbered prefix).
4. Else ask the user where to put it. Don't silently create files in the project root.

If the user invokes this skill in a directory with no obvious project (no git, no `docs/`), say so and ask before doing anything.

## Add mode

The user has a single item to file. Goal: lower ceremony than typing the issue themselves. If it's heavier than that, they'll stop using the skill.

1. **Dupe check.** Search existing items for keyword overlap (`gh issue list --search "<keywords>"` or grep the local file). If a near-match exists, surface it and ask whether to update that one or file new. This is the cheapest defence against ending up with three issues for the same thing.

2. **Enhance proportional to input.** A one-liner from the user warrants 2-3 short context bullets drawn from CLAUDE.md and the current project state (technical caveats, related modules, open questions). If the user already wrote a paragraph or more, file it as-is. Don't restructure their words. The point of enhancement is to capture context they didn't bother to type, not to dress up what they did type.

3. **One clarifying question max**, and only when scope or category (bug vs enhancement) is genuinely ambiguous. If you can guess from context, guess.

4. **File and return the URL or path.** No trailing summary; the URL is the receipt.

### Labels

GitHub: pick from `gh label list`. Don't invent new labels without asking. Projects often have label conventions wired into filters, project boards, or release automation, and an invented label is invisible to those.

Local `docs/BACKLOG.md` or per-issue files: prefix the title with `[bug]` / `[enhancement]` / `[question]` for easy scanning.

## Review mode

The user wants to see what's open and possibly act on something.

1. **List.**
   - GitHub: `gh issue list --state open --limit 50 --json number,title,labels,createdAt`.
   - Local file: read it and parse the bullet/heading structure.
   - Per-issue files: list filenames with their first-line title.

2. **Group and present.** By label first (bug / enhancement / question / other), then by age within each group. One line per item: number, title, age, label. Don't paginate unless the list is genuinely long (>50 items).

3. **Offer three actions** without auto-picking:
   - **Triage**: re-label, close stale items, merge duplicates. Per-item confirmation.
   - **Pick one**: load the full item into context and stop. Do not auto-implement; the user might be scanning the backlog before deciding what to focus on.
   - **Themes**: cluster related items, suggest groupings or parent issues.

The "pick one" action is deliberately a stop point. Sliding into implementation work breaks the user's actual flow, which was reviewing.

## Gotchas

- **Don't bulk-close in triage.** "Close the stale ones" almost always means show them first, then close after confirmation. Wrong-close is much more expensive than an extra confirmation step.
- **Don't invent labels.** `gh label list` is cheap; respecting existing label conventions matters because labels drive filters and project boards downstream.
- **Capture must be lighter than typing the issue manually.** The "one clarifying question max" rule isn't about being terse; it's about preserving the value proposition. If the skill takes longer than the user just typing it, they'll stop using it.
- **Per-issue local files need a numbering scheme.** When using `docs/issues/`, look at existing files (`0001-slug.md`? `001-slug.md`?) and continue the existing scheme. Don't impose a new one.
- **Project root pollution.** If no `gh`, no `docs/BACKLOG.md`, no `docs/issues/`, ask. Silently creating `BACKLOG.md` in the project root surprises the user.
- **Don't restructure the user's words.** If they wrote a paragraph, file the paragraph. Reformatting into your preferred template feels like the AI is overwriting their intent, even if the template is "better".
- **Respect issue templates.** If the repo has `.github/ISSUE_TEMPLATE/`, conform the body to the matching template (typically bug vs feature). `gh issue create --title --body` skips templates silently, which surprises maintainers who built filters or automations around the template's fields.

Versions

RepositoryScoreLicence
This page · sammcj/agentic-coding90Apache-2.0
Ovid/paad100MIT
Ovid/paad100MIT
Ovid/paad100MIT
gtlpanda/PandaStack100MIT
SergioLizana/Dynamo100MIT
bitIO/wheelhouse100MIT
Archont561/qgis-agent-harness100MIT
umputun/cc-thingz100MIT

Database snapshot: 13.11.2026 · package version a44153860d90 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Backlog Management
    This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md.
  • 100github-backlog-triage
    Use when the user invokes backlog triage for a GitHub repo''s open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
  • 100issue-triage
    Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
  • 100triage-backlog
    Triage BACKLOG items for continued validity — verify each item's claim against the current tree and rule it keep / already-delivered / partially-delivered / duplicate / retire, with evidence per verdict. Use when the user asks to triage the backlog, check whether an item is…
  • 100issue-tracking
    Use when user mentions issue, bug, task, ticket, feature, backlog, tracking, or work items. Suggests using Trekker for tracking.
  • 100ratchet-backlog
    Create, validate, extend, groom, and migrate ratchet BACKLOG.md files — from TODO/FIXME comments, GitHub issues, a PRD/notes file, or plain conversation. Enforces the ratchet:v1 and ratchet:v2 contracts, especially the core invariant "no acceptance criteria, no item"; v2 adds…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.