Sprint Planner
Turn a backlog and team capacity into a committed sprint plan.
Before & after
Same prompt, same agent — the only difference is the skill.
A 2-week sprint with a team of 6 is a good size. You'll want to think about what your key priorities are, how much work you can realistically fit, and making sure everyone has clear tasks. It's helpful to do some estimation so you know your team's capacity. You might want to reserve some time for bugs or tech debt. Communication is important—maybe a daily standup keeps everyone aligned. You'll probably want to review the sprint at the end to see how you did. Identifying blockers early helps. It really depends on your current project status and what the business needs most. What are the main things you're trying to ship in the next sprint?
SPRINT BACKLOG (2 weeks, 6 devs, 8 SP/dev = 48 SP total capacity) PRIORITY 1: Authentication redesign (product request, shifts launch) • User profile SSO integration: 5 SP → assigned to dev1, dev2 (pairs on first 3 days) • OAuth token refresh logic: 3 SP → dev3 • Logout clear sessions endpoint: 2 SP → dev4 SUBTOTAL: 10 SP PRIORITY 2: Performance regression fix (blocking enterprise trial) • DB query optimization (reports page): 5 SP → dev5 (SQL + testing) • Caching layer implementation: 5 SP → dev6 SUBTOTAL: 10 SP PRIORITY 3: Tech debt & bugs (reserve 20% sprint) • Flaky test suite: 3 SP → dev1 (after SSO) • Dependency security updates: 2 SP → rotating owner, 30min daily SUBTOTAL: 5 SP BUFFER & CARRYOVER: 18 SP (37% reserve for shifting asks) KNOWN RISKS • OAuth provider API changes mid-sprint → mitigate with mock server • Reports data volume test may reveal new bottleneck → escalate immediately VALIDATION: Standup daily 10am, blockers tracked in shared log. Friday retro: compare estimate to actual per person.
About this skill
name: sprint-plan description: Use when Structured Claude skill that gives Claude a repeatable workflow for sprint plan.
Sprint Plan
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Sprint Plan workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the sprint-plan skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Sprint Plan; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: sprint-plan
description: Use this skill when a development team needs a repeatable workflow for producing a sprint plan.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Sprint Plan
Gives a repeatable workflow for turning a backlog and team capacity into a committed sprint plan.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.