agentleFS
Sign inStart free
sammcjsammcj/agentic-coding/Skills/backlog/SKILL.md

backlog

Skill167 starsChanged 10 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a section, or a new file continuing the existing numbering (0001-slug.md).

    line 21
  2. Very specific:

    Add: write the body to a file in a mktemp -d directory, then gh issue create --body-file <file>.

    line 27
  3. Distinctive:

    Search for dupes first. On a near match, ask: update it or file new.

    line 31
  4. Distinctive:

    Keep the contents concise, quick and easy to read.

    line 45
  5. Distinctive:

    Use the users wording, if you have context you may add it, if clarification is required: ask, do not make up requirements.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 35 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free