Skip to content

borghei/Claude-Skills / business-operations/capacity-planner

capacity-planner

Verified

Headcount and delivery-capacity planning — effective capacity from raw headcount, hire/contract/defer scenarios, and capacity-vs-commitment gap reports. Use when planning a quarter, sizing a hiring ask, or testing whether a roadmap fits.

assets/capacity-plan-template.md

View on GitHub
# Capacity Plan — [Team] — [Quarter]

**Owner:** [name] · **Prepared:** [date] · **Status:** Draft / Reviewed / Committed

> Assumptions used where inputs were unavailable are listed in section 6.

---

## 1. Headline

| | |
|---|---|
| Effective capacity | [X] hours ([Y] delivery-FTE) |
| Committable after buffer | [X] hours |
| Adjusted demand | [X] hours |
| **Gap** | **[+/- X] hours ([Z]% loaded)** |
| Status | GREEN / AMBER / RED |

**One-line summary:** [e.g. "Engineering is 213% loaded; four committed items
are above the cut line and need renegotiation this week."]

---

## 2. Supply — effective capacity

Generated by `capacity_model.py`.

| Discipline | FTE | Gross h | Effective h | Ratio |
|-----------|-----|---------|-------------|-------|
| Engineering | | | | |
| Design | | | | |
| QA | | | | |
| **Total** | | | | |

**Ramping this quarter:** [names, seniority, ramp multiplier]

**Supply assumptions:**
- Working days: [X] · Hours/day: [X]
- Buffer for unplanned work: [X]% — basis: [trailing actuals / default]
- On-call rotation size: [X] people
- Known leave already deducted: [yes/no]

---

## 3. Demand — commitments

Generated by `commitment_gap.py`.

### Above the line (committed)

| # | Item | Discipline | Raw h | Adjusted h | Confidence | External commitment |
|---|------|-----------|-------|-----------|-----------|---------------------|
| 1 | | | | | | |
| 2 | | | | | | |

### Below the cut line (not committed this quarter)

| # | Item | Discipline | Adjusted h | Why it was cut | Next candidate slot |
|---|------|-----------|-----------|----------------|---------------------|
| | | | | | |

**Committed items at risk:** [list — these need renegotiation now, with named
owner and date for the conversation]

---

## 4. Gap options

Generated by `scenario_compare.py`.

| Scenario | Hours added (horizon) | Total cost | Cost/hour | Demand met | Relief starts |
|----------|----------------------|-----------|-----------|-----------|---------------|
| Cut scope | | 0 | — | | Immediate |
| Reduce overhead | | 0 | — | | 2-4 weeks |
| Defer | | 0 | — | | Immediate |
| Contract | | | | | Q+0/Q+1 |
| Hire | | | | | Q+2 |

**Recommendation:** [scenario] — [rationale in one or two sentences, covering
time to relief, cost per hour, reversibility, and knowledge retention]

**Decision needed by:** [date] · **Decision owner:** [name]

---

## 5. Risks

| Risk | Trigger to watch | Impact if it lands | Mitigation |
|------|-----------------|--------------------|-----------|
| Ramp slower than modelled | [new hire] below 50% by week 6 | [X] h shortfall | Assign buddy; reduce their on-call exemption period |
| Unplanned work exceeds buffer | Unplanned share > [X]% for 2 weeks | Cut line moves up by [X] items | Pre-agreed drop list, in priority order |
| Key-person dependency | [name] unavailable | [item] stalls | Pair a second person from week 1 |
| Attrition | Any resignation | 5-8 months to effective replacement | [backfill posture] |

---

## 6. Assumptions

1. [Estimation confidence bands assigned by [who], on [date]]
2. [Buffer of X% based on ...]
3. [Ramp curves: library defaults / team-measured]
4. [Anything unknown at time of writing, and what would resolve it]

---

## 7. Tracking

| Week | Planned burn (h) | Actual burn (h) | Burn ratio | Unplanned share | Action |
|------|-----------------|-----------------|-----------|-----------------|--------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |

**Replan trigger:** burn ratio above 1.15 at week 4, or unplanned share above
the buffer for two consecutive weeks.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall