scrum-backlog-refinement

Refines Product Backlogs by splitting epics into INVEST user stories traced to RUP use cases.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill scrum-backlog-refinement-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrum-backlog-refinement
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/scrum-backlog-refinement
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill scrum-backlog-refinement-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product Backlogs often contain oversized epics and vague items that stall Sprint Planning. This Skill guides the continuous refinement activity: breaking epics into vertical user stories, validating them against INVEST criteria, estimating with story points, and enforcing a Definition of Ready so only prepared items reach Sprint Planning. ## Core Features & Use Cases - Epic Decomposition: Split epics into vertical, end-to-end stories using workflow, business-rule, data-variation, and CRUD splitting patterns. - INVEST & DoR Validation: Check every top-of-backlog story against the six INVEST criteria and an explicit Definition of Ready checklist. - RUP Traceability: Anchor each user story to its source UC-XXX use case, inheriting acceptance criteria instead of inventing them. - Use Case: A team with a large checkout epic uses this Skill to split it into stories like cart review, shipping entry, and payment, each estimated in Fibonacci story points and traced to its RUP use case before Sprint Planning. ## Quick Start Refine the top of our Product Backlog by splitting the checkout epic into INVEST-compliant user stories traced to their UC identifiers.

Frequently Asked Questions about scrum-backlog-refinement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split an epic into user stories?▼

Split epics vertically using patterns like workflow steps, business rules, data variations, or CRUD operations so each story delivers end-to-end value. Avoid splitting by technical layers like backend and frontend, since neither half delivers value alone.

What are the INVEST criteria for user stories?▼

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. A story failing Estimable or Small goes back for splitting, while one failing Testable needs concrete acceptance criteria agreed with the Product Owner.

What is a Definition of Ready in Scrum?▼

A Definition of Ready is the entry contract for Sprint Planning: a story must use the As a/I want/So that format, cite its source use case, have verifiable acceptance criteria, carry a Fibonacci estimate, pass INVEST, and have documented dependencies.

When should backlog refinement not be used?▼

Do not use refinement to commit a Sprint or build the Sprint Backlog, which belongs to Sprint Planning, or to elicit requirements from scratch, which belongs to business analysis. Refinement assumes existing requirements such as documented use cases.

Why should user stories trace back to use cases?▼

Tracing each story to a UC-XXX use case keeps the backlog anchored to verified requirements and lets stories inherit acceptance criteria instead of inventing them. A story without a source use case signals a requirements gap that must be documented first.