AgentSkillsCN

scrum-event-backlog-refinement

将 PBI 转化为可直接交付给 AI 执行的就绪状态。适用于精炼待办事项、编写验收标准、拆分用户故事,或确保“就绪定义”的达成。

SKILL.md
--- frontmatter
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.

You are an 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.

  • Splitting & Merging: See splitting.md for when to split large PBIs AND when to merge small ones back together
  • Anti-Patterns: See anti-patterns.md for common PBI mistakes to avoid

AI-Agentic Definition of Ready

Ready = AI can complete it without asking humans.

A PBI is ready when:

  1. AI can complete without human input
  2. User Story format (role, capability, benefit)
  3. Acceptance criteria have executable verification commands
  4. Dependencies are resolved
  5. INVEST principles are satisfied

INVEST Principles (AI-Agentic)

PrincipleAI-Agentic Interpretation
IndependentCan reprioritize freely, AND no human dependencies
NegotiableClear outcome, flexible implementation
ValuableUser Story format makes value explicit
EstimableAll information needed is available
SmallSmallest unit delivering user value
TestableHas executable verification commands

Refinement Process

  1. Autonomous Refinement First - Explore codebase, propose acceptance criteria, identify dependencies
  2. If AI Can Fill All Gaps - Update status to ready
  3. If Story Is Too Big - Split into smaller stories (see splitting.md)
  4. If Story Lacks Value Alone - Merge with adjacent PBI (see splitting.md Anti-Patterns)
  5. If Needs Human Help - Keep as refining, document questions

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

Backlog Granularity

code
┌─────────────────┐
│  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.

Collaboration

  • @scrum-team-product-owner: Product Goal alignment, value prioritization
  • @scrum-team-developer: Technical feasibility, effort estimation
  • @scrum-team-scrum-master: Definition of Ready enforcement