agentleFS
Sign inStart free
adrianoanthonymma16-boopadrianoanthonymma16-boop/opencode-agents/skills/gsd-review-backlog/SKILL.md

gsd-review-backlog

Skill1 starsChanged 58 days agoMITView on GitHub

Review and promote backlog items to active milestone

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 0 are distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Update ROADMAP.md: move the entry from ## Backlog section to the active phase list

    line 36
  2. Very specific:

    Add appropriate Depends on: field

    line 38
  3. Common:

    Delete the phase directory

    line 41
  4. Very specific:

    Remove the entry from ROADMAP.md ## Backlog section

    line 42

“Common” is measured: kept by at least 6 in 10 of the 4 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
<objective> Review all 999.x backlog items and optionally promote them into the active milestone sequence or remove stale entries. </objective><process>
  1. List backlog items:
    _BACKLOG=( .planning/phases/999* )
if [ -e "${_BACKLOG[0]}" ]; then ls -d "${_BACKLOG[@]}"; else echo "No backlog items found"; fi
  2. Read ROADMAP.md and extract all 999.x phase entries:
    cat .planning/ROADMAP.md
    Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
  3. Present the list to the user via question:
    • For each backlog item, show: phase number, description, accumulated artifacts
    • Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
  4. For items to PROMOTE:
    • Find the next sequential phase number in the active milestone
    • Rename the directory from 999.x-slug to {new_num}-slug:
      NEW_NUM=$(gsd-tools query phase.add "${DESCRIPTION}" --raw)
    • Move accumulated artifacts to the new phase directory
    • Update ROADMAP.md: move the entry from ## Backlog section to the active phase list
    • Remove (BACKLOG) marker
    • Add appropriate **Depends on:** field
  5. For items to REMOVE:
    • Delete the phase directory
    • Remove the entry from ROADMAP.md ## Backlog section
  6. Commit changes:
    gsd-tools query commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
  7. Report summary:
    ## 📋 Backlog Review Complete

Promoted: {list of promoted items with new phase numbers}
Kept: {list of items remaining in backlog}
Removed: {list of deleted items}
</process>

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