agentleFS
link7373link7373/agentic-pmo/.claude/skills/groom-backlog/SKILL.md

groom-backlog

Skill1 starsChanged 3 months agoMITView on GitHub

Write and refine the product backlog — break epics into INVEST user stories, add testable acceptance criteria, estimate, and order to Definition of Ready. Use to prepare work for sprints. Dispatches the product-owner. Supports optional tool sync.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Write each as As a <user>, I want <capability>, so that <outcome> with testable acceptance criteria.

    line 19
  2. Very specific:

    Update knowledge/backlog.md (source of truth).

    line 30
  3. Very specific:

    Follow standards/document-standards.md and standards/agile-standards.md.

    line 31
  4. Very specific:

    If knowledge/integrations.md configures a tool (Jira/Linear/Notion), after updating knowledge/backlog.md offer to sync new/changed stories …

    line 34

“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

/groom-backlog — Make work ready

When to use

Turning roadmap/PRD intent into well-formed, ordered, ready backlog items; ongoing refinement.

Dispatches

product-owner (lead). Consult scrum-master for readiness/estimation facilitation.

Inputs

knowledge/roadmap.md, PRDs, knowledge/product-context.md, existing knowledge/backlog.md.

Steps

  1. Pull intent from roadmap/PRDs; break epics into thin, valuable stories.
  2. Write each as As a <user>, I want <capability>, so that <outcome> with testable acceptance criteria; capture non-functional needs (performance, security, accessibility) as explicit, measurable items too.
  3. Enforce INVEST; split oversized stories into end-to-end slices; keep each item traceable to a need/goal.
  4. Estimate (story points / t-shirt) per standards/agile-standards.md; note dependencies.
  5. Order the backlog by value/priority; bring top items to Definition of Ready.

Methods

knowledge/methods/requirements-and-stories.md, knowledge/methods/business-analysis.md, knowledge/methods/agile-scrum-mechanics.md, knowledge/methods/prioritization-frameworks.md.

Output

Update knowledge/backlog.md (source of truth); log ordering/scope decisions to knowledge/decision-log.md. Follow standards/document-standards.md and standards/agile-standards.md.

Optional sync

If knowledge/integrations.md configures a tool (Jira/Linear/Notion), after updating knowledge/backlog.md offer to sync new/changed stories to it via the available connector. Files remain the source of truth; if no integration is configured, skip silently.


Created by Colin Beck<br> LinkedIn: https://www.linkedin.com/in/beckcolin/<br> GitHub: https://github.com/link7373

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.