Sprint Planner
Run a structured agile sprint planning session with story points, capacity math, and a committed backlog table your agent can paste into Notion or Linear.
Overview
Sprint Planner is an agent skill most often used in Build (also Operate) that facilitates agile sprint planning with story points, capacity, velocity, and a formatted sprint backlog.
Install
npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill sprint-plannerWhat is this skill?
- Modified Fibonacci story points (1, 2, 3, 5, 8, 13, 20) with explicit estimation framing
- Capacity formula: team × days × hours × focus factor (0.6–0.8)
- Velocity guidance from the last 3–5 sprints
- Markdown sprint backlog table with owner and dependency columns
- Risks, mitigation, and Definition of Done checklist in every plan
- Modified Fibonacci scale: 1, 2, 3, 5, 8, 13, 20
- Focus factor range 0.6–0.8 in capacity formula
- Velocity averaged over past 3–5 sprints
Adoption & trust: 2.2k installs on skills.sh; 114k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a backlog and a date range but no clear sprint goal, capacity-backed commitment, or shared Definition of Done before coding starts.
Who is it for?
Solo or tiny teams running scrum-like sprints on a SaaS or product backlog who want Fibonacci estimates and capacity math in one shot.
Skip if: Kanban-only continuous flow with no sprint boundaries, or teams that already have a locked sprint plan in Jira and only need ticket edits.
When should I use this skill?
Planning sprints, estimating stories, defining sprint goals, managing sprint backlogs, or when user mentions sprint planning, agile, scrum, story points, or sprint capacity.
What do I get? / Deliverables
You get a named sprint with goal, dates, capacity vs committed points, backlog table, risks, and DoD—ready to break into tasks or hand to a writing-plans skill.
- Markdown sprint plan with goal, capacity, committed points, backlog table, risks, and Definition of Done
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Sprint planning is the canonical PM ritual while you are actively building and shipping iterations, not one-off idea research. The skill outputs sprint goals, backlog tables, and DoD checklists—core product-management artifacts during the build phase.
Where it fits
Commit sprint backlog and DoD before your agent starts implementation tasks for the milestone.
Rough-size MVP epics into points to see if the prototype scope fits one sprint.
Re-plan the next sprint after production feedback without losing velocity context.
How it compares
Structured sprint ceremony in chat instead of blank Notion pages or generic “help me plan this week” without capacity math.
Common Questions / FAQ
Who is sprint-planner for?
Indie builders and small squads who mention sprint planning, scrum, story points, or sprint capacity and want a facilitator-style plan without hiring a scrum master.
When should I use sprint-planner?
During Build PM when starting an iteration; during Operate iterate when re-planning the next cycle; anytime you are estimating stories, defining sprint goals, or prioritizing sprint backlog items.
Is sprint-planner safe to install?
Review the Security Audits panel on this Prism page and the MIT-licensed SKILL.md in the repo before enabling it in your agent.
SKILL.md
READMESKILL.md - Sprint Planner
# Sprint Planner You are an expert scrum master who facilitates effective sprint planning for agile teams. ##When to Apply Use this skill when: - Planning sprint iterations - Estimating user stories with story points - Defining sprint goals - Managing sprint capacity - Prioritizing backlog items - Identifying sprint dependencies and risks ## Sprint Planning Framework Story Points: Use Modified Fibonacci: 1, 2, 3, 5, 8, 13, 20 Team Capacity: (Team × Days × Hours × Focus Factor 0.6-0.8) Velocity: Average points completed in past 3-5 sprints ## Output Format ```markdown ## Sprint [Number]: [Name] **Sprint Goal**: [Clear objective] **Duration**: [Dates] **Capacity**: [Points] **Committed**: [Points from backlog] ## Sprint Backlog | Story | Points | Owner | Dependencies | |-------|--------|-------|--------------| | [ID-Description] | [Pts] | [Name] | [None/Story IDs] | ## Risks & Mitigation [List potential issues and how to handle] ## Definition of Done - [ ] Code reviewed - [ ] Tests passing - [ ] Deployed to staging - [ ] PO approval ``` --- *Created for Agile/Scrum sprint planning workflows*