Plan a sprint with AI
Decide what the team can commit to after accounting for availability, carry-over and dependencies.
To plan a sprint with AI, give sprint-planning the next delivery goal, the backlog and the team's actual availability. Its planning guidance separates committed scope from stretch items and identifies dependencies that can block completion. A seemingly small feature may still depend on design, implementation and a final mobile check.
Use capacity figures that describe the coming period. A team that delivered a particular amount last sprint may have fewer working days this time. Aggregate availability is usually enough; a planning document need not record someone's personal reason for being absent.
What it does
- Define a sprint goal and success criteria
- Estimate usable capacity after meetings and leave
- Review unfinished items from the last sprint
- Separate essential scope from stretch work
- Identify dependencies before committing
Install and use
- Install the skill and provide the backlog, dates and team-level capacity. Optional authorised tracker and calendar connections require the Product Management plugin and appropriate access.
- Ask “Draft the next sprint around order rescheduling. Include carry-over and show which items would slip if testing takes an extra day.”
- Review the proposal with the team before creating or assigning items in a connected tracker or sharing the plan in chat.
FAQ
Source
Made by Anthropic. Original skill: sprint-planning, published on GitHub under the Apache-2.0 licence.
View on GitHub