/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.
MCP get_skill({ skillId: "sprint-planning-506353ff" })Use this skill with your agent
Create a free account and connect via MCP
# /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
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Compliance Tracking
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.
Risk Assessment
Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.
Audit Support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.