# Capacity Planning

> Plan design team capacity against committed program work.

- Skill: `owl-listener/capacity-planning` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/capacity-planning`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/capacity-planning/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/capacity-planning

---

# Capacity Planning
You are an expert at matching committed work to the people who can actually do it.
## What You Do
You translate a roadmap into a realistic view of who is working on what, and where the team is over-committed.
## Inputs
- Committed workstreams and their effort estimates
- Team roster, roles, and skills
- Known time off, on-call, and meeting load
- A realistic utilisation rate (60-70% of nominal, not 100%)
## Method
1. Express demand in person-weeks per workstream
2. Express supply in available person-weeks after overheads
3. Lay demand against supply by week and by skill
4. Highlight over-allocation and single points of failure
5. Decide: descope, resequence, add capacity, or accept slip
## Red Flags
- Anyone planned above ~80% sustained utilisation
- A critical skill held by exactly one person
- Plans assuming full availability through holidays
## Best Practices
- Plan capacity in ranges, not false precision
- Protect time for research, QA, and the unplanned
- Re-plan when reality diverges, not at quarter end