Backlog Groom

Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.

9 starsOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add flurdy/agent-skills --skill backlog-groom
Manual install
git clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backlog-groom ~/.claude/skills/backlog-groom

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Backlog Groom — Per-Bead Quality Audit

Walk the **selected backlog** and ask, for each bead: *is this any good?* Flag hygiene, priority, lifecycle, structure, and duplicate problems, propose a concrete fix for each, and **only mutate on explicit approval**.

This is the hygiene counterpart to the intake/reconciliation skills — it is the only one that systematically reads every bead in scope and improves its quality.

## Relationship to other tools

- **`/triage`** is *forward intake*: prompt/Jira → new bead(s), with dup-check and splitting **at creation time**. The groomer does not create beads from prompts and does not re-implement splitting — when a bead obviously needs splitting, it hands the bead to `/triage`.
  - **`/triage <bead-id>`** (refine mode) is the *depth* counterpart to this sweep: it investigates one existing bead against the code, then deepens, corrects, or splits it. Hand a bead there whenever grooming it needs real investigation rather than a one-shot edit — see the "be fast" rule below.
  - **`/refine <bead-id>`** is the read-only *sizing* judgement: keep whole, clarify, or split. Hand a bead there when the open question is whether it is one outcome or several; it routes any approved change back through `/triage`.
- **`/tracking-sweep`** is *cross-system drift* (Jira ↔ beads ↔ PRs), read-only. The groomer does not re-implement cross-system linking — when a bead lacks a Jira/Trello link, it flags it and points at `/tracking-sweep` (or `/trello-beads`).
Read the full skill on GitHub

Details

Skill name
backlog-groom
Path
skills/backlog-groom/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Backlog Groom skill do?

Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.

How do I install the Backlog Groom skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill backlog-groom. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Backlog Groom popular?

It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.