agentsclimarketplace

Sprint planner

Skill mb3rgel-ui/atlas-claude-skill/skills/sprint-planner

Atlas — Engineering Agent for Claude Code. Sprint planning, standup, task management, and coding agent loops.

Install
npx -y skills add mb3rgel-ui/atlas-claude-skill --skill sprint-planner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

2.7 KB, 723 tokens by cl100k_base, as published. Nobody here has run it

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

# 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]
  1. 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."

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.