Backlog Refinement Expert

Backlog Refinement Expert

Overview

Refinement is the most under-invested ritual in agile teams. Stories arrive at sprint planning oversized, ambiguous, or strategically disconnected, and the team spends planning meetings doing what should have happened the week before. This skill is the refinement playbook: grade stories against INVEST, split them vertically (so each slice ships value end-to-end), and keep a working Definition of Ready and Definition of Done that prevent half-baked work from entering or leaving a sprint.

The skill includes a Python scorer (refinement_scorer.py) that grades each story in a JSON backlog against the six INVEST criteria and outputs a readiness score (0-6) per story. Stories scoring 5-6 are sprint-ready; 3-4 need targeted refinement; below 3 go back to discovery.

This complements wwas/ (Why-What-Acceptance format) and job-stories/ (JTBD format). Either format produces stories; this skill grades them and gets them sprint-ready.

Core Capabilities

• INVEST grading — score each story across Independent, Negotiable, Valuable, Estimable, Small, Testable (0-6) and triage by score.
• Vertical story splitting — the 9 Lawrence recipes + SPIDR taxonomy; avoid horizontal (layer/team/sprint) splits.
• Definition of Ready / Done — input and output quality gates with enforceable templates.
• Refinement session structure — cadence, candidate volume, triage routing into discovery or planning.

When to Use

• Weekly refinement session -- grade next-sprint candidates against INVEST and split anything too large.
• Backlog hygiene sweep -- re-grade the top 30 items and retire what no longer connects to strategy.
• Sprint planning input -- confirm all candidates pass DoR before planning.
• New team onboarding -- establish a shared definition of "ready" and "done."
• Velocity diagnosis -- erratic sprint completion usually traces to refinement quality.

When NOT to use: pure technical task lists with no user-facing outcome (use a simpler checklist); ad-hoc bug triage (different lifecycle); unscoped work (send to discovery/ first).

Clarify First

Before grading the backlog, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• The stories — the actual backlog items in the user's words, with their acceptance criteria (drives every INVEST score and which slicing recipe applies)
• Team's Definition of Ready — what "ready" means for THIS team (DoR must be team-authored to be enforced; sets the promote/refine/return gate)
• Sprint size / "small enough" bar — sprint length and rough capacity (sets how far a story must be split before it counts as Small)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start