sprint-planning
Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.
Best use case
sprint-planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.
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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sprint-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sprint-planning Compares
| Feature / Agent | sprint-planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.
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.
Related Guides
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# /sprint-planning > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Plan a sprint by scoping work, estimating capacity, and setting clear goals. ## Usage ``` /sprint-planning $ARGUMENTS ``` ## How It Works ``` ┌─────────────────────────────────────────────────────────────────┐ │ SPRINT PLANNING │ ├─────────────────────────────────────────────────────────────────┤ │ STANDALONE (always works) │ │ ✓ Define sprint goals and success criteria │ │ ✓ Estimate team capacity (accounting for PTO, meetings) │ │ ✓ Scope and prioritize backlog items │ │ ✓ Identify dependencies and risks │ │ ✓ Generate sprint plan document │ ├─────────────────────────────────────────────────────────────────┤ │ SUPERCHARGED (when you connect your tools) │ │ + Project tracker: Pull backlog, create sprint, assign items │ │ + Calendar: Account for PTO and meetings in capacity │ │ + Chat: Share sprint plan with the team │ └─────────────────────────────────────────────────────────────────┘ ``` ## What I Need From You - **Team**: Who's on the team and their availability this sprint? - **Sprint length**: How many days/weeks? - **Backlog**: What's prioritized? (Pull from tracker, paste, or describe) - **Carryover**: Anything unfinished from last sprint? - **Dependencies**: Anything blocked on other teams? ## Output ```markdown ## Sprint Plan: [Sprint Name] **Dates:** [Start] — [End] | **Team:** [X] engineers **Sprint Goal:** [One clear sentence about what success looks like] ### Capacity | Person | Available Days | Allocation | Notes | |--------|---------------|------------|-------| | [Name] | [X] of [Y] | [X] points/hours | [PTO, on-call, etc.] | | **Total** | **[X]** | **[X] points** | | ### Sprint Backlog | Priority | Item | Estimate | Owner | Dependencies | |----------|------|----------|-------|--------------| | P0 | [Must ship] | [X] pts | [Person] | [None / Blocked by X] | | P1 | [Should ship] | [X] pts | [Person] | [None] | | P2 | [Stretch] | [X] pts | [Person] | [None] | ### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity) ### Risks | Risk | Impact | Mitigation | |------|--------|------------| | [Risk] | [What happens] | [What to do] | ### Definition of Done - [ ] Code reviewed and merged - [ ] Tests passing - [ ] Documentation updated (if applicable) - [ ] Product sign-off ### Key Dates | Date | Event | |------|-------| | [Date] | Sprint start | | [Date] | Mid-sprint check-in | | [Date] | Sprint end / Demo | | [Date] | Retro | ``` ## Tips 1. **Leave buffer** — Plan to 70-80% capacity. You will get interrupts. 2. **One clear sprint goal** — If you can't state it in one sentence, the sprint is unfocused. 3. **Identify stretch items** — Know what to cut if things take longer than expected. 4. **Carry over honestly** — If something didn't ship, understand why before re-committing.
Related Skills
org-planning
Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
pipeline-review
Analyze pipeline health — prioritize deals, flag risks, get a weekly action plan. Use when running a weekly pipeline review, deciding which deals to focus on this week, spotting stale or stuck opportunities, auditing for hygiene issues like bad close dates, or identifying single-threaded deals.
forecast
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
draft-outreach
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
daily-briefing
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
create-an-asset
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
competitive-intelligence
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
call-summary
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.