sprint-planning
Use when facilitating sprint planning, refining the backlog, calculating team capacity, or setting sprint goals
Works with
--- name: sprint-planning description: Use when facilitating sprint planning, refining the backlog, calculating team capacity, or setting sprint goals license: MIT --- # Sprint Planning ## When to Use At the start of each sprint to align the team on what to build and why. ## Process Checklist ### Pre-Planning (day before) - [ ] Backlog groomed — top items have acceptance criteria and estimates - [ ] Previous sprint velocity calculated (avg of last 3 sprints) - [ ] Team capacity confirmed (who's out? on-call? support rotation?) - [ ] Product goal for this sprint drafted ### The Planning Meeting (2 hours max for 2-week sprint) **Part 1: Why (30 min)** - PO presents sprint goal — the one outcome this sprint delivers - Team asks clarifying questions - Goal is agreed (not just "ship features", but "users can complete checkout") **Part 2: What (60 min)** - Pull from top of backlog until capacity is reached - Capacity = velocity × (available dev-days / sprint-days) - Each story: confirm understanding of acceptance criteria - If unclear: clarify now or push to next sprint **Part 3: How (30 min)** - Break stories into tasks (optional, but recommended for complex stories) - Identify dependencies between tickets - Flag risks: what could go wrong? ### Capacity Calculation ``` Available dev-days = (team_size × sprint_days) - PTO - meetings - support_rotation Capacity = (available_dev_days / sprint_days) × historical_velocity ``` ### Sprint Goal Formula "By the end of this sprint, [user type] will be able to [capability], which enables [business outcome]." ## Core Jobs - Calculate team capacity accurately - Define a clear sprint goal (not just a list of tickets) - Commit to a realistic sprint backlog - Surface risks before the sprint starts ## Key Outputs - Sprint goal (one sentence) - Sprint backlog (committed stories) - Capacity breakdown - Risk log ## Anti-Patterns - No sprint goal — just a list of tickets - Committing to 100% capacity (no buffer for unknowns) - Adding tickets during the sprint without removing others - Planning stories that aren't ready (no acceptance criteria)
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.
