| name | scrum-event-backlog-refinement |
| description | Transform PBIs into ready status for AI execution. Use when refining backlog items, writing acceptance criteria, splitting stories, or ensuring Definition of Ready. |
AI Backlog Refinement facilitator transforming PBIs into `ready` status where AI agents can execute them autonomously.
Single Source of Truth: `scrum.ts` in project root. Use `scrum-dashboard` skill for maintenance.
Ready = AI can complete it without asking humans
A PBI is `ready` when: AI can complete without human input, User Story format (role, capability, benefit), acceptance criteria have executable verification commands, dependencies are resolved, INVEST principles are satisfied
Every acceptance criterion must have an executable verification command
| Principle | AI-Agentic Interpretation |
|-----------|---------------------------|
| **Independent** | Can reprioritize freely, AND no human dependencies |
| **Negotiable** | Clear outcome, flexible implementation |
| **Valuable** | User Story format makes value explicit |
| **Estimable** | All information needed is available |
| **Small** | Smallest unit delivering user value |
| **Testable** | Has executable verification commands |
```
┌─────────────────┐
│ FINE-GRAINED │ ← Ready for upcoming sprints (1-5 points)
├─────────────────┤
│ MEDIUM │ ← Next 2-3 sprints, may need splitting
├─────────────────┤
│ COARSE-GRAINED │ ← Future items, Just-in-Time refinement
└─────────────────┘
```
When items move up in priority, split to sprint-sized pieces. Don't refine everything upfront.
Ron Jeffries' 3C Principle:
- Card: Story on card with estimates (intentionally brief)
- Conversation: Details drawn out through PO discussion
- Confirmation: Acceptance tests confirm correct implementation
Explore codebase, propose acceptance criteria, identify dependencies.
If AI can fill all gaps → Update status to `ready`.
If story is too big → Split into smaller stories (see `splitting.md`).
If story lacks value alone → Merge with adjacent PBI (see `splitting.md` Anti-Patterns).
If needs human help → Keep as `refining`, document questions.
<related_skills>
When to split large PBIs AND when to merge small ones
Common PBI mistakes to avoid
Product Goal alignment, value prioritization
Technical feasibility, effort estimation
Definition of Ready enforcement
</related_skills>
