Capacity Planning
Plan team capacity for "$ARGUMENTS" across upcoming sprints. List team members, calculate available working days accounting for holidays and leave, apply focus factors, estimate capacity in story points, and identify capacity risks over the next 3-6 sprints.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"project-management-capacity-planning","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill. It can be run at any time, with or without existing project artifacts.
If .singularskills/project-management/<project>/ exists, read any available artifacts for context (especially team setup, sprint metrics, and velocity data). If it does not exist, proceed based on information the user provides.
Process
Gather context:
- If
.singularskills/project-management/<project>/ exists, read available artifacts for team composition, velocity history, and sprint cadence
- If no artifacts exist, ask the user for: team members, sprint length, and upcoming sprint dates
- Determine the planning horizon: typically 3-6 sprints ahead
List team members with their roles:
- For each team member, document:
- Name and role (developer, designer, QA, etc.)
- Allocation — full-time (100%) or part-time (specify percentage)
- Individual velocity — if known from historical data (story points per sprint)
- Skills or specialties — useful for identifying single points of failure
- Note any planned team changes: new hires joining, members departing, role changes
For each sprint period, calculate available working days:
- Total business days in the sprint (exclude weekends)
- Minus public holidays — list specific holidays that fall in the sprint
- Minus known PTO and leave — planned vacations, sick leave patterns, parental leave, training days
- Minus company events — offsites, all-hands, hackathons, conferences
- Calculate per person and as a team total
- Present as a table: team member x sprint with available days in each cell
Subtract overhead:
- Meetings and ceremonies — sprint planning, standup, review, retro, backlog refinement (typically 15-20% of time)
- Support and maintenance — on-call duties, production support, bug triage (estimate based on historical patterns)
- Administrative tasks — code reviews, documentation, mentoring, hiring interviews
- Default overhead: 20% of available time, adjust based on team's actual experience
- Document the overhead percentage used and rationale
Apply focus factor:
- Focus factor accounts for context switching, interruptions, and ramp-up time
- 0.8 (high focus): dedicated team, minimal interruptions, mature processes
- 0.7 (normal): typical team with some interruptions and context switching
- 0.6 (low focus): frequent interruptions, multiple projects, many ad-hoc requests
- Select the appropriate factor based on the team's working environment
- Document the chosen factor and rationale
Calculate capacity in story points per sprint:
- Formula: available days x (1 - overhead%) x focus factor x individual velocity factor
- If individual velocity is unknown, use a default of 1 story point per productive day as a starting point
- If team historical velocity is known, use it as a cross-check:
- Calculate capacity bottom-up (sum of individual capacities)
- Compare with top-down (historical team velocity adjusted for availability)
- Use the lower of the two estimates for safer planning
- Present capacity per person and as a team total for each sprint
Sum team capacity per sprint:
- Create a summary table: sprint x total capacity (story points)
- Show the range: minimum (pessimistic), expected (realistic), maximum (optimistic)
- Compare with backlog demand if known — is there enough capacity to deliver the planned work?
- Highlight sprints with significantly reduced capacity (holidays, leaves)
Identify capacity risks across the planning horizon:
- Holiday clusters — sprints with multiple holidays reducing capacity significantly
- Planned leaves — periods where multiple team members are out simultaneously
- Key-person dependencies — sprints where a specialist is unavailable and work depends on them
- Ramp-up periods — new team members who will not be at full velocity initially (expect 25-50% for first sprint, 50-75% for second)
- Competing priorities — known events that will pull team members away (releases, on-call rotations, company events)
- For each risk, note the impact on capacity and suggest mitigation (shift work, cross-train, adjust scope)
Recommend commitment levels per sprint:
- Based on calculated capacity, recommend how many story points to commit to in each sprint
- Commitment guideline: commit to 80% of calculated capacity to leave room for unknowns
- Flag sprints where capacity is below 70% of normal — consider reducing scope or extending timelines
- Flag sprints where commitment should be especially conservative (first sprint of a new team, post-holiday sprints)
- Suggest which work to prioritize or defer based on capacity constraints
Write the artifact — save to .singularskills/project-management/<project>/capacity-planning.md:
- Team Roster — members, roles, allocation, and velocity
- Sprint Calendar — dates, business days, holidays, and PTO for each sprint
- Capacity Table — available days, overhead, focus factor, and story points per person per sprint
- Team Capacity Summary — total capacity per sprint with min/expected/max range
- Capacity Risks — identified risks with impact and mitigation
- Commitment Recommendations — recommended story point commitment per sprint
- Assumptions — overhead percentage, focus factor, velocity factors used
Output
Capacity plan saved to .singularskills/project-management/<project>/capacity-planning.md. Present a summary highlighting:
- Team size and total capacity across the planning horizon
- Sprints with significantly reduced capacity and why
- Top capacity risk and recommended mitigation
- Commitment recommendations per sprint
1---2name: project-management-capacity-planning3description: Plan capacity over the next 3-6 sprints from availability, holidays, leave and focus factor, with risks and suggested commitments. Use when leave, holidays or team changes are coming and the user asks how many people-days the coming sprints have. Not for past velocity or choosing this sprint's stories; see /project-management-velocity-analysis or /project-management-sprint-planning.4metadata:5 source: https://skillmd.com/skills/bromso/project-management-capacity-planning6 argument-hint: "[project] [--skip-checks]"7---89# Capacity Planning1011Plan team capacity for "$ARGUMENTS" across upcoming sprints. List team members, calculate available working days accounting for holidays and leave, apply focus factors, estimate capacity in story points, and identify capacity risks over the next 3-6 sprints.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"project-management-capacity-planning","workflow":"project-management","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Prerequisites1617None — this is a utility skill. It can be run at any time, with or without existing project artifacts.1819If `.singularskills/project-management/<project>/` exists, read any available artifacts for context (especially team setup, sprint metrics, and velocity data). If it does not exist, proceed based on information the user provides.2021## Process22231. **Gather context:**24 - If `.singularskills/project-management/<project>/` exists, read available artifacts for team composition, velocity history, and sprint cadence25 - If no artifacts exist, ask the user for: team members, sprint length, and upcoming sprint dates26 - Determine the planning horizon: typically 3-6 sprints ahead27282. **List team members with their roles:**29 - For each team member, document:30 - **Name** and **role** (developer, designer, QA, etc.)31 - **Allocation** — full-time (100%) or part-time (specify percentage)32 - **Individual velocity** — if known from historical data (story points per sprint)33 - **Skills or specialties** — useful for identifying single points of failure34 - Note any planned team changes: new hires joining, members departing, role changes35363. **For each sprint period, calculate available working days:**37 - **Total business days** in the sprint (exclude weekends)38 - **Minus public holidays** — list specific holidays that fall in the sprint39 - **Minus known PTO and leave** — planned vacations, sick leave patterns, parental leave, training days40 - **Minus company events** — offsites, all-hands, hackathons, conferences41 - Calculate per person and as a team total42 - Present as a table: team member x sprint with available days in each cell43444. **Subtract overhead:**45 - **Meetings and ceremonies** — sprint planning, standup, review, retro, backlog refinement (typically 15-20% of time)46 - **Support and maintenance** — on-call duties, production support, bug triage (estimate based on historical patterns)47 - **Administrative tasks** — code reviews, documentation, mentoring, hiring interviews48 - Default overhead: 20% of available time, adjust based on team's actual experience49 - Document the overhead percentage used and rationale50515. **Apply focus factor:**52 - Focus factor accounts for context switching, interruptions, and ramp-up time53 - **0.8 (high focus):** dedicated team, minimal interruptions, mature processes54 - **0.7 (normal):** typical team with some interruptions and context switching55 - **0.6 (low focus):** frequent interruptions, multiple projects, many ad-hoc requests56 - Select the appropriate factor based on the team's working environment57 - Document the chosen factor and rationale58596. **Calculate capacity in story points per sprint:**60 - **Formula:** available days x (1 - overhead%) x focus factor x individual velocity factor61 - If individual velocity is unknown, use a default of 1 story point per productive day as a starting point62 - If team historical velocity is known, use it as a cross-check:63 - Calculate capacity bottom-up (sum of individual capacities)64 - Compare with top-down (historical team velocity adjusted for availability)65 - Use the lower of the two estimates for safer planning66 - Present capacity per person and as a team total for each sprint67687. **Sum team capacity per sprint:**69 - Create a summary table: sprint x total capacity (story points)70 - Show the range: minimum (pessimistic), expected (realistic), maximum (optimistic)71 - Compare with backlog demand if known — is there enough capacity to deliver the planned work?72 - Highlight sprints with significantly reduced capacity (holidays, leaves)73748. **Identify capacity risks across the planning horizon:**75 - **Holiday clusters** — sprints with multiple holidays reducing capacity significantly76 - **Planned leaves** — periods where multiple team members are out simultaneously77 - **Key-person dependencies** — sprints where a specialist is unavailable and work depends on them78 - **Ramp-up periods** — new team members who will not be at full velocity initially (expect 25-50% for first sprint, 50-75% for second)79 - **Competing priorities** — known events that will pull team members away (releases, on-call rotations, company events)80 - For each risk, note the impact on capacity and suggest mitigation (shift work, cross-train, adjust scope)81829. **Recommend commitment levels per sprint:**83 - Based on calculated capacity, recommend how many story points to commit to in each sprint84 - **Commitment guideline:** commit to 80% of calculated capacity to leave room for unknowns85 - Flag sprints where capacity is below 70% of normal — consider reducing scope or extending timelines86 - Flag sprints where commitment should be especially conservative (first sprint of a new team, post-holiday sprints)87 - Suggest which work to prioritize or defer based on capacity constraints888910. **Write the artifact** — save to `.singularskills/project-management/<project>/capacity-planning.md`:90 - **Team Roster** — members, roles, allocation, and velocity91 - **Sprint Calendar** — dates, business days, holidays, and PTO for each sprint92 - **Capacity Table** — available days, overhead, focus factor, and story points per person per sprint93 - **Team Capacity Summary** — total capacity per sprint with min/expected/max range94 - **Capacity Risks** — identified risks with impact and mitigation95 - **Commitment Recommendations** — recommended story point commitment per sprint96 - **Assumptions** — overhead percentage, focus factor, velocity factors used9798## Output99100Capacity plan saved to `.singularskills/project-management/<project>/capacity-planning.md`. Present a summary highlighting:101- Team size and total capacity across the planning horizon102- Sprints with significantly reduced capacity and why103- Top capacity risk and recommended mitigation104- Commitment recommendations per sprint