Sprint Planner

Sprint Planner is a ready-to-run product management skill on Zeplik. Use to plan a sprint -- scope work against team capacity (accounting for PTO and meetings), set the sprint goal, P0 vs stretch calls, carryover from last sprint, draft the sprint plan. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.

The Sprint Planner skill loads automatically when your request matches it, or you can invoke it directly by typing /sprint-planning in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.

What the Sprint Planner skill can do

• Calculate team capacity accounting for PTO and meetings
• Set a single clear sprint goal and success criteria
• Prioritize backlog items into P0, P1, and stretch tiers
• Generate a full sprint plan doc with risks and key dates

Try these prompts on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

• Help me plan our 2 week sprint starting Monday, team of 5 engineersTry on Zeplik
• We have 3 carryover tickets from last sprint, how should I factor those inTry on Zeplik
• Sarah is out 3 days on PTO this sprint, help me recalculate capacityTry on Zeplik
• Draft a sprint plan for the checkout redesign backlog I'm pasting inTry on Zeplik

How the Sprint Planner skill works

/sprint-planning $ARGUMENTS

┌─────────────────────────────────────────────────────────────────┐
│                    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                        │
└─────────────────────────────────────────────────────────────────┘

## 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 |

How to use the Sprint Planner skill

1. 1

   Sign in to Zeplik

   Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Sprint Planner skill right away.

2. 2

   Describe your product management task

   Ask in plain language, or type /sprint-planning to invoke the skill directly. Zeplik recognizes the Sprint Planner skill and applies its method.

3. 3

   Review and refine the result

   Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.

Source and credit

Frequently asked questions

What is the Sprint Planner skill?

Sprint Planner is a ready-to-run product management skill on Zeplik. Use to plan a sprint -- scope work against team capacity (accounting for PTO and meetings), set the sprint goal, P0 vs stretch calls, carryover from last sprint, draft the sprint plan. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.

How do I use Sprint Planner on Zeplik?

Sign in to Zeplik and ask in plain language, or type /sprint-planning in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.

Which AI model does the Sprint Planner skill use?

Any model you choose. Zeplik works across every model in one chat, so the Sprint Planner skill runs on your preferred model for the task.

Where does the Sprint Planner skill come from?

The Sprint Planner skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.

How much does the Sprint Planner skill cost?

Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.

Related product skills

• Agile Product OwnerUse when writing INVEST user stories, acceptance criteria, or grooming and prioritizing a product backlog. Not for sprint ceremony planning (use sprint-planning).
• AI Product BuilderUse when building a paid product that wraps AI APIs: architecture, prompts as product, cost metering, differentiation. Not for calling the Anthropic API in code (use claude-api).
• AI Product DevelopmentIntegration, safety and cost guidance for building or hardening a production LLM feature. Not for a thin one-API SaaS (use ai-wrapper-product).
• Game-Changing FeaturesStack-ranked 10x opportunity analysis across massive/medium/small bets. Not for open-ended ideation (use product-brainstorming) or one idea into a spec (use idea-to-spec).
• Idea to SpecTurn a rough product idea into build-ready documents through staged gates: a clarifying interview in chat, then a design doc artifact, an optional UI brief, and an implementation plan. Use when the user has an app or feature idea and wants it captured, shaped, and specified before any code. Not for tasks that already have a clear spec (use plan or execplan) or for pure research questions.
• Pre-Build Risk ReviewUse for a pre-build risk review of demand, positioning, monetization, retention, distribution before committing to build. Not for turning an idea into a full spec (use idea-to-spec).