# Sprint Planner

> Atlas sprint planning — build sprints from backlog, track velocity, run sprint reviews, and propose next sprint. Use when planning a new sprint, reviewing a completed sprint, or checking sprint velocity.

- Skill: `mb3rgel-ui/sprint-planner` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mb3rgel-ui/sprint-planner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mb3rgel-ui/sprint-planner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: mb3rgel-ui (https://skillmd.com/u/mb3rgel-ui)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mb3rgel-ui/sprint-planner

---


# Sprint Planner — Atlas

Plan sprints, track velocity, review performance.

## Sprint Planning

### Start Sprint Planning
"Plan sprint" / "Plan next sprint" / "Sprint kickoff"

1. Read `memory/backlog.md` — load all unscheduled tasks
2. Sort by priority: P1 first, then P2, then P3
3. Check final deadline from IDENTITY.md — calculate weeks remaining
4. Propose 5–7 tasks for this sprint (never more than 7)
5. For each proposed task: show title, priority, estimated effort (S/M/L)
6. Ask: "Approve this sprint or adjust?"
7. On approval: write to `memory/sprint.md`, remove tasks from backlog.md

### Sprint Rules
- Max 7 tasks per sprint
- All P1 tasks from backlog go first
- If backlog has 0 P1 tasks: ask user to reprioritize before planning
- Sprint goal = one sentence describing what success looks like this week

### Sprint Format in memory/sprint.md

```markdown
# Sprint [N] — Week of YYYY-MM-DD

**Sprint Goal:** [one sentence]
**Final Deadline:** YYYY-MM-DD
**Weeks Remaining:** [N]

## Tasks

- [ ] [P1] Task title | deadline: YYYY-MM-DD | owner: solo
- [ ] [P1] Task title | deadline: YYYY-MM-DD | owner: solo
- [ ] [P2] Task title | deadline: YYYY-MM-DD | owner: solo
```

## Sprint Review

### Run Sprint Review
"Sprint review" / "How did the sprint go?" / "Friday review"

1. Read `memory/sprint.md` — count total tasks
2. Read `memory/done.md` — count tasks completed this sprint (filter by this week's dates)
3. Read `memory/blocked.md` — what was blocked and why?
4. Calculate velocity: (done / total) × 100

### Review Output Format

```
Sprint [N] Review — YYYY-MM-DD

Velocity: [N]/[N] tasks shipped ([%]%)

Shipped:
- [x] Task 1
- [x] Task 2

Slipped:
- [ ] Task 3 — reason: [why]

Blockers this sprint:
- [blocker] — resolved/unresolved

Velocity trend: Week 1: 71% | Week 2: 85% | Week 3: [%]

Next sprint recommendation: [cut scope / maintain / stretch]
```

5. Ask: "Ready to plan next sprint?"

## Velocity Tracking

Atlas tracks sprint velocity over time in `memory/done.md`.

Each completed task gets a completion entry:
```
- [x] [P1] Task title | completed: YYYY-MM-DD | sprint: [N]
```

Velocity is calculated weekly during sprint review.
If velocity < 60% for 2 sprints in a row: Atlas recommends cutting backlog by 30%.

## Backlog Grooming

"Groom backlog" / "Reprioritize"

1. Read `memory/backlog.md`
2. Show all tasks grouped by priority
3. Ask: "Any tasks to reprioritize, remove, or add?"
4. Rewrite backlog with updated priorities
5. Confirm: "Backlog groomed. [N] P1 tasks, [N] P2, [N] P3."