Before selecting, verify Definition of Ready:
- Clear user story with role, action, benefit
- Acceptance criteria specific and testable
- Dependencies identified and resolved
- No blocking questions remaining
- Has executable verification commands

Characteristics:
- Evaluable: Can clearly determine if achieved
- Stakeholder-Understandable: Meaningful outside the team
- Outcome-Focused: Value delivered, not tasks completed
- Fixed: Does not change during Sprint

Working backwards - ask:
- "What do we want to demonstrate at Sprint Review?"
- "What would make stakeholders excited?"
- "What can we show as a working increment?"

Subtask format in `scrum.ts`:
```yaml
subtasks:
  - test: "What behavior to verify (RED phase)"
    implementation: "What to build (GREEN phase)"
    type: behavioral  # behavioral | structural
    status: pending   # pending | red | green | refactoring | completed
    commits: []
    notes: []
```

Subtask types:
- `behavioral`: New functionality (RED → GREEN → REFACTOR)
- `structural`: Refactoring only (skips RED/GREEN, goes to refactoring)

<best_practices> Keep subtasks small (completable in one TDD cycle) Order by logical dependency Each subtask independently testable Update status immediately when completing Mark type: behavioral or structural </best_practices>

<anti_patterns> "Complete all Sprint Backlog items" (not a goal) "Finish Stories A, B, and C" (output-focused) Goals only developers understand </anti_patterns>

<related_skills> Sprint Goal input, Product Backlog prioritization Task breakdown, technical feasibility Facilitation, impediment removal </related_skills>

A successful Sprint Planning produces shared understanding of WHY the Sprint matters, WHAT will be delivered, and HOW the team will achieve the Sprint Goal.

scrum-event-sprint-planning