Sprint Planning

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

FeaturedInstructions onlyProductivity & Workflow
AI-generated overview

Plans a sprint by scoping work, estimating team capacity, setting goals, and drafting a sprint plan document.

What it does
Guides an agent through sprint planning: defining sprint goals and success criteria, estimating team capacity while accounting for PTO and meetings, scoping and prioritizing backlog items, and identifying dependencies and risks. It produces a sprint plan document with capacity, backlog, risks, definition of done, and key dates. It can optionally pull backlog items, create sprints, and share the plan when project tracker, calendar, and chat tools are connected.
When to use it
Use when kicking off a new sprint, sizing a backlog against team availability, deciding what is P0 versus stretch, or handling carryover from the previous sprint.
Requirements
Instructions only; no scripts. Works standalone, but can optionally use connected project tracker, calendar, and chat tools for pulling backlog, creating sprints, and sharing the plan.

/sprint-planning

If you see unfamiliar placeholders or need to check which tools are connected, see 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.

Source and attribution

Source:anthropics/knowledge-work-pluginsinproduct-management/skills/sprint-planningat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today