Part of Build Product Features With PM Guidance
Product & Design Blueprint
Safety checkedPlan Sprints With Capacity Math
A skill that organizes backlog items into a sprint with capacity checks, priority ordering, risk flagging, and stretch goals.
What problem does this solve?
Plans sprints with capacity math so teams commit to what they can actually finish instead of overloading and missing. It takes your backlog, team size, and sprint duration; calculates available capacity (80% ceiling); slots items by priority and dependencies; flags risks and unresolved requirements; and paces stretch goals for if the team finishes early. The output is a sprint plan a PM can hand to engineering without ambiguity.
How does it work?
- Say 'plan sprint' or 'what should we work on?'. 2. Claude asks for your backlog (titles, estimates, priorities), team size, sprint duration (1 or 2 weeks), and constraints. 3. It calculates capacity (team size times days times 80%), slots items, identifies dependencies and blockers, and flags risks with mitigations. It generates: sprint goal (1 sentence), recommended backlog with ownership and dependencies, capacity verdict (over/under/right-sized), stretch goals, and risks to watch. Output: a sprint plan that's realistically sized and explicitly handles risk.
Included Skills
No skills in this group
What's required to run this?
Triggered by 'plan sprint', 'sprint planning', 'what should we work on', or 'organize the backlog'. Works with estimates in engineer-days or story points. Enforces 80% capacity ceiling; plans above this have 50%+ failure rate.
Key Features
Capacity Math
Calculates available eng-days at 80% ceiling. Slots items to fit. Verdict: over-sized (fails 50%+ of sprints), right-sized, or under-sized.
Dependency Mapping
Identifies blockers and dependencies between items so nothing gets started before its prerequisite is done.
Priority Ordering
Slots P0 items first (critical-path), then P1 (important), then P2 (nice-to-have). P0 items get top team capacity.
Risk Flagging
Identifies uncertain estimates, unresolved requirements, and blockers with mitigation plans. Example: 'Mobile bug estimate uncertain; if not resolved by Wednesday, descope and carry to next sprint.'
Stretch Goals
Low-priority items or research tasks the team can pull in if they finish early. Prevents idle capacity and keeps momentum.
Tools in this Blueprint
About This Blueprint
- Industry
- Technology
More Blueprints to explore
⭐ Ask Nicely : Find your next reviewers
Pick promoters from your CRM, remove accounts with open escalations, overdue billing or a recent review, then create the G2 review campaign after you approve the list, send method and any incentive.
G2CRMSurvey or CS platform+4 moreCharlie Albuery
🤝 You Said We Did : Align your roadmap to real user feedback
Group recent G2 reviews into themes, check each theme against tickets in your work tracker, and return a ranked one-page brief that lists the themes with no ticket first.
G2Work trackerResearch repository+3 moreCharlie Albuery
👀 Wandering Eyes : Identify churn risk early
Match accounts renewing soon in your CRM to G2 buyer intent on competitors and your category, check usage, support and meetings, then rank the accounts and brief the CSM. Runs as a weekly sweep or on one named account.
G2CRMProduct usage analytics+4 moreCharlie Albuery