scrum-backlog-refinement

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/jcg-admin/kaupamex-api --skill scrum-backlog-refinement-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrum-backlog-refinement
Source: https://github.com/jcg-admin/kaupamex-api/tree/main/.claude/skills/scrum-backlog-refinement
Command: npx skills add https://github.com/jcg-admin/kaupamex-api --skill scrum-backlog-refinement-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product Backlogs often contain oversized epics and vague items that derail 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 sprint-ready items reach planning. ## Core Features & Use Cases - Epic decomposition: Split large epics into vertical, value-delivering stories using patterns like workflow steps, business rules, data variations, and CRUD operations. - INVEST validation and estimation: Check each story against all six INVEST criteria and estimate with planning poker on a Fibonacci scale, flagging anything 13+ points for further splitting. - RUP traceability: Anchor every story to a UC-XXX use case via the :uc_origen: field, inheriting acceptance criteria instead of inventing them. - Use Case: A Product Owner preparing for Sprint Planning on an e-commerce checkout epic uses this Skill to split it into cart, shipping, payment, and confirmation stories, each estimated, INVEST-compliant, and traced to its RUP use case. ## Quick Start Ask the assistant to refine the checkout epic from the Product Backlog into INVEST-compliant user stories traced to their UC use cases with story point estimates and a Definition of Ready checklist.

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 for Scrum?▼

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 more splitting, while one failing Testable needs concrete acceptance criteria worked out with the Product Owner.

What is a Definition of Ready in Scrum backlog refinement?▼

A Definition of Ready is the entry contract for Sprint Planning: the story uses the As a/I want/So that format, traces to a source use case, has verifiable acceptance criteria, carries a Fibonacci estimate, passes INVEST, and has documented dependencies.

When should I not use backlog refinement?▼

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 elicitation. Refinement starts from existing requirements like documented use cases.

How do user stories stay traceable to RUP use cases?▼

Each story cites its source use case in a uc_origen field and inherits its acceptance criteria rather than inventing new ones. If the source use case is incomplete, the use case is corrected first before deriving the story.