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
- microsoft/agent-host-protocoltheir own version, first seen Nov 13, 2026
- shady2k/skillstheir own version, first seen Oct 11, 2026
- Sassy-Dog/skillstheir own version, first seen Oct 8, 2026
- gioe/tusktheir own version, first seen May 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- microsoft/agent-host-protocol★ 453same name
- shady2k/skills★ 6same name
- gioe/tusk★ 1same name
- Sassy-Dog/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
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
- Very specific: line 19
Write each as As a <user>, I want <capability>, so that <outcome> with testable acceptance criteria.
- Very specific: line 30
Update knowledge/backlog.md (source of truth).
- Very specific: line 31
Follow standards/document-standards.md and standards/agile-standards.md.
- Very specific: line 34
If knowledge/integrations.md configures a tool (Jira/Linear/Notion), after updating knowledge/backlog.md offer to sync new/changed stories …
“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.
Files
/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
- Pull intent from roadmap/PRDs; break epics into thin, valuable stories.
- 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. - Enforce INVEST; split oversized stories into end-to-end slices; keep each item traceable to a need/goal.
- Estimate (story points / t-shirt) per
standards/agile-standards.md; note dependencies. - 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
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
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.

