Sprint Planning

Plan implementation sprints with story selection, goal definition, and execution ordering.

509 stars

Best use case

Sprint Planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Plan implementation sprints with story selection, goal definition, and execution ordering.

Teams using Sprint Planning should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/sprint-planning/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/bmad-method/skills/sprint-planning/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/sprint-planning/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Sprint Planning Compares

Feature / AgentSprint PlanningStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Plan implementation sprints with story selection, goal definition, and execution ordering.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Sprint Planning

Plan implementation sprints with story selection, goal definition, and execution ordering.

## Agent
Bob (Scrum Master) - `bmad-sm-bob`

## Workflow
1. Review available stories from epic backlog
2. Consider velocity from previous sprints
3. Select stories forming coherent sprint goal
4. Validate stories are implementation-ready
5. Order by dependency and priority
6. Define sprint goal and identify blockers

## Inputs
- `projectName` - Project name
- `sprintNumber` - Current sprint number
- `epics` - Available epics and stories
- `previousSprints` - Previous sprint results (optional)

## Outputs
- Sprint goal and selected stories
- Execution order with dependencies
- Story point commitment
- Blocker identification

## Process Files
- `bmad-orchestrator.js` - Phase 4 sprint planning
- `bmad-implementation.js` - Standalone implementation