[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754EWAD4FC6H35ZKA7NMJ72":3,"skill-same:01M754EWAD4FC6H35ZKA7NMJ72":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":13,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M754EWAD4FC6H35ZKA7NMJ72","capacity-planner",null,"Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the team is growing >50% in 12 months. Run before committing the headcount budget. This is NOT engineering capacity (see vpe-advisor for DORA + cycle time) and NOT strategic 3-year workforce planning (see chro-advisor).","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: capacity-planner\ndescription: \"Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the team is growing >50% in 12 months. Run before committing the headcount budget. This is NOT engineering capacity (see vpe-advisor for DORA + cycle time) and NOT strategic 3-year workforce planning (see chro-advisor).\"\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, capacity, headcount, utilization, queueing-theory, ops-planning, little-law, workforce]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# capacity-planner\n\nSizing tool for **ops teams that handle queued work** — Support, CX,\nCustomer Success, BizOps, IT ops, Finance ops. Built on Erlang-C\nqueueing theory, Little's Law, and the operational-leadership canon\n(Fournier, Larson, Cleveland, Reinertsen). Deterministic, stdlib-only,\nno LLM calls.\n\n## Purpose\n\nYou are an ops leader sized 15 → 35 with no idea how the 35-person org\nwill actually behave at peak load. Or you are at 88% utilization and\nSLA is starting to slip. Or you have a hiring budget approved and need\nto sequence it across four quarters without burning out the existing\nteam. This skill answers those questions with arithmetic, not vibes.\n\nIt produces three artifacts:\n\n1. **Capacity sizing** at 70\u002F80\u002F90% utilization against P50\u002FP90\u002FP99\n   demand, with P(SLA breach) at each point and a SAFE\u002FWATCH\u002FAT_RISK\u002FCRITICAL\n   risk band.\n2. **Utilization health** at the per-member traffic-light level plus a\n   team verdict (HEALTHY\u002FSQUEEZED\u002FOVERLOADED\u002FUNBALANCED).\n3. **12-month quarterly hiring plan** accounting for ramp curves,\n   attrition, QoQ demand growth, and span-of-control manager triggers.\n\n## When to use\n\n- **Annual ops capacity planning** (October-November for the following\n  fiscal year).\n- **Quarterly re-sizing** if demand changed >15% or attrition spiked.\n- **Pre-budget defense** — the math that justifies the headcount ask\n  to your CFO.\n- **Diagnostic** when an ops team is missing SLA and you need to know\n  whether it's a sizing problem, a process problem, or a bottleneck\n  problem.\n- **M&A \u002F new-segment launch** modeling — sizing a new team or\n  combined org.\n\n## Workflow\n\n1. **Intake demand**. Pull P50\u002FP90\u002FP99 daily ticket\u002Fcase volume from\n   your work system (Zendesk, Intercom, JSM, ServiceNow, Salesforce).\n   If you only have averages, stop and pull the distribution. Single-\n   point demand estimates are the most expensive anti-pattern in ops.\n2. **Model throughput**. Run `capacity_modeler.py` with your demand,\n   AHT, SLA target, current FTE, and shrinkage. Use `--profile` for\n   your function (support \u002F cx \u002F bizops \u002F finance-ops \u002F it-ops). Read\n   the 80%-utilization row — that's your sizing point.\n3. **Flag utilization risk**. Run `utilization_analyzer.py` against\n   your current team's actual utilization data. Anyone >85% sustained\n   is a throughput-collapse risk per Reinertsen. Spread >30 percentage\n   points across team means UNBALANCED — fix that before hiring.\n4. **Sequence hiring**. Run `hiring_sequencer.py` with current FTE,\n   target EOY, ramp time, attrition, and growth. It will front-load\n   hires (Q1 35%, Q4 15%), apply ramp curves, and trigger a manager\n   hire when span of control crosses 7 ICs\u002Fmanager.\n5. **Walk the Forcing-question library** (see below). One question at\n   a time. Do not skip ahead. Answers must be written down before\n   you commit the plan.\n\n## Scripts\n\n- `scripts\u002Fcapacity_modeler.py` — Erlang-C sizing with shrinkage\n  adjustment and P50\u002FP90\u002FP99 breach probabilities. `--profile`\n  for industry defaults.\n- `scripts\u002Futilization_analyzer.py` — per-member traffic-light +\n  team-level health verdict with variance detection.\n- `scripts\u002Fhiring_sequencer.py` — 12-month quarterly plan with ramp,\n  attrition, growth, max-hires-per-quarter constraint, and\n  manager-trigger logic.\n\nAll three accept `--input \u003Cpath>` (JSON), `--output {markdown,json}`,\n`--sample` (built-in example), and `--help`. Stdlib only.\n\n## References\n\n- `references\u002Fqueueing_theory_canon.md` — Erlang, Little, Hopp &\n  Spearman, Reinertsen, Kingman, Cleveland, ITIL, Armony et al. (8\n  sources). The math.\n- `references\u002Fops_workforce_planning_canon.md` — Fournier, Larson,\n  Google SRE Workbook, Frei, Lawler, Bersin, Gartner, Grove (8\n  sources). The people factors.\n- `references\u002Fcapacity_anti_patterns.md` — 11 named anti-patterns\n  with cited sources, tool guards, and the meta-discipline that\n  Lencioni + Goldratt + Christensen impose. (8+ named sources.)\n\n## Assets\n\n- `assets\u002Fcapacity_brief_template.md` — 20-minute fill-out template\n  with JSON skeletons for all three tools and an output checklist.\n\n## Assumptions\n\nThis skill assumes:\n\n- Work is **queued** (tickets, cases, work items) — not project-style.\n  If your team's work isn't queued, this is the wrong skill.\n- Demand has a **stationary-enough distribution** within a quarter.\n  Step-changes (new product launch, M&A, regulatory shift) require\n  re-running mid-quarter.\n- You have **at least 90 days of historical demand data** to compute\n  P50\u002FP90\u002FP99. If not, generate the distribution from your sales \u002F\n  user-base forecast first.\n- Service is **single-class** within a queue. If you have hard\n  priority tiers (P1\u002FP2\u002FP3 with class-specific SLAs), model each as\n  a separate queue and sum.\n- **Channels are modeled coherently.** Multi-channel teams use the\n  appropriate `--profile` with built-in shrinkage premium.\n\n## Anti-patterns\n\nSee `references\u002Fcapacity_anti_patterns.md` for the full taxonomy with\nsources. Top eight:\n\n1. Plan-to-100%-utilization (Reinertsen Principle 12)\n2. Treat-ramp-as-instant (Larson)\n3. Ignore-attrition-in-12-month-plan (Bersin)\n4. Hire-ICs-forever-with-no-manager-trigger (Fournier)\n5. Size-to-P50-demand-only (Cleveland)\n6. No-shrinkage-adjustment (Cleveland, SRE Workbook)\n7. Single-channel-model-for-multi-channel-work (Gartner, Kingman)\n8. No-surge-plan-for-P99-events (Hopp & Spearman, Reinertsen)\n\n## Distinct from\n\n- **`c-level-advisor\u002Fvpe-advisor`** measures *engineering* throughput\n  via DORA 4 metrics, story points, deployment frequency, and cycle\n  time bottlenecks. It is for engineering teams shipping code. This\n  skill is for ops teams handling tickets\u002Fcases. Different unit of\n  work, different math (Erlang-C vs. DORA), different bottleneck\n  (queueing-blind staffing vs. WIP + lead time).\n- **`c-level-advisor\u002Fchro-advisor`** does *strategic* workforce\n  planning (1-5 year capability portfolios, talent supply, leadership\n  succession). This skill does *operational* 0-12 month capacity\n  sizing against demand. Per Lawler: conflating them gets you hired\n  into the wrong jobs.\n- **`project-management\u002F*`** tracks delivery throughput on projects\n  (Jira velocity, sprint capacity). This skill sizes around steady-\n  state queued work.\n- **Sibling `process-mapper`** *finds* the bottleneck. This skill\n  *sizes the team around* a known bottleneck. Order of operations:\n  process-mapper first → capacity-planner second. Hiring around the\n  wrong constraint wastes the hires.\n- **`business-growth\u002Fcs-coverage`** (if it exists) sizes Customer\n  Success coverage by ARR\u002FCSM ratio and segment. This skill sizes by\n  queued work volume (tickets, cases, escalations). For a CS team\n  that handles both relationship work AND a ticket queue, run both.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\n**Discipline**: walk these one at a time. Do not skip ahead. Answers must\nbe written down. If you can't answer one, that is your next investigation.\n\n### Q1 — \"What is your bottleneck, and have you confirmed it empirically?\"\n\n**Recommended answer**: a named, measured stage in the workflow with\nqueue-time data showing where work waits. Not a vibe. Not \"escalations\ntake too long\". An actual measured queue.\n\n**Why it's the first question**: Goldratt (*The Goal*, 1984) — every\nsystem has exactly one binding constraint at a time. Sizing around the\nwrong constraint wastes hires entirely. If you do not know your\nbottleneck, run `process-mapper` BEFORE this skill.\n\n**Canon**: Eli Goldratt, *The Goal* (1984); Reinertsen, *Principles of\nProduct Development Flow* (2009).\n\n### Q2 — \"What service trade-off are you accepting?\"\n\n**Recommended answer**: a written, explicit choice — fast vs. empathetic,\nbroad vs. deep, low-cost vs. high-quality. Frances Frei is unambiguous:\nyou cannot win all four. The team that tries wins zero.\n\n**Why it matters**: AHT, SLA, and shrinkage inputs are the operational\nexpression of this trade-off. If they don't agree (e.g., you set AHT for\n\"empathy\" but SLA for \"speed\"), the plan is internally inconsistent.\n\n**Canon**: Frances Frei & Anne Morriss, *Uncommon Service* (HBR Press,\n2012).\n\n### Q3 — \"What's your demand P90, and what's the gap to your P99?\"\n\n**Recommended answer**: two specific numbers from the last 90 days of\ndata, with the calendar context of each (e.g., \"P90 was 480 tickets\u002Fday\non normal Tuesdays; P99 was 720 on the day after the November release\").\nA team sized to P50 misses SLA half the time. A team sized to P99\noverstaffs by 30-50%. P90 is the right operating sizing point per\nCleveland.\n\n**Canon**: Brad Cleveland, *Call Center Management on Fast Forward* (4th\ned., 2019); A.K. Erlang, *The Theory of Probabilities and Telephone\nConversations* (1909).\n\n### Q4 — \"At your planned utilization, what is P(SLA breach) at P90 and at P99?\"\n\n**Recommended answer**: two probabilities, computed (not guessed) from\nErlang-C with your specific N, AHT, and SLA target. If P(breach at P90)\n> 10% you are understaffed at the sizing point. If P(breach at P99) >\n50% you have no surge plan and the next peak event will be visible to\nthe CEO.\n\n**Canon**: Erlang (1909); Hopp & Spearman, *Factory Physics* (3rd ed.,\n2008), VUT equation.\n\n### Q5 — \"Have you budgeted replacement hires for the attrition you'll see this year?\"\n\n**Recommended answer**: yes, with a specific number. At 30% annual\nattrition (Bersin BPO midpoint), a 20-FTE team loses ~6 people this year.\nIf your \"add 5 net\" plan is actually a \"hire 11\" plan, the recruiting\nvolume changes drastically. Anti-pattern #3.\n\n**Canon**: Bersin\u002FDeloitte talent benchmarks (2015-2023); Edward Lawler,\n*Strategic Workforce Planning* (USC CEO, 2008).\n\n### Q6 — \"When does span of control trigger a manager hire, and who is the candidate?\"\n\n**Recommended answer**: a specific quarter (from `hiring_sequencer.py`)\nand at least one identified candidate (internal lead or external hire).\nPast 7 ICs\u002Fmanager, 1:1s degrade, feedback cycles slip, attrition\nclimbs. Past 10 you have a coverage crisis. Hire the manager BEFORE\ncrossing 10, not after.\n\n**Canon**: Camille Fournier, *The Manager's Path* (O'Reilly, 2017),\nch. 5; Andy Grove, *High Output Management* (1983).\n\n### Q7 — \"What is your surge plan for the P99 day?\"\n\n**Recommended answer**: an explicit, documented plan — overflow tier,\nBPO contracted capacity, on-call rotation, executive escalation tree,\nOR a written degradation contract that says \"on P99 days we extend SLA\nto X minutes and notify customers proactively\". If the answer is \"we'll\nfigure it out\", the P99 day is a fire visible to the board.\n\n**Canon**: Hopp & Spearman, *Factory Physics* (2008); Reinertsen (2009)\non capacity-margin discipline.\n\n---\n\n**Walk these seven in order. One at a time. Write the answers down. The\nplan you submit is only as defensible as your answers to these seven\nquestions.**\n","# capacity-planner\n\nSizing tool for **ops teams that handle queued work** — Support, CX,\nCustomer Success, BizOps, IT ops, Finance ops. Built on Erlang-C\nqueueing theory, Little's Law, and the operational-leadership canon\n(Fournier, Larson, Cleveland, Reinertsen). Deterministic, stdlib-only,\nno LLM calls.\n\n## Purpose\n\nYou are an ops leader sized 15 → 35 with no idea how the 35-person org\nwill actually behave at peak load. Or you are at 88% utilization and\nSLA is starting to slip. Or you have a hiring budget approved and need\nto sequence it across four quarters without burning out the existing\nteam. This skill answers those questions with arithmetic, not vibes.\n\nIt produces three artifacts:\n\n1. **Capacity sizing** at 70\u002F80\u002F90% utilization against P50\u002FP90\u002FP99\n   demand, with P(SLA breach) at each point and a SAFE\u002FWATCH\u002FAT_RISK\u002FCRITICAL\n   risk band.\n2. **Utilization health** at the per-member traffic-light level plus a\n   team verdict (HEALTHY\u002FSQUEEZED\u002FOVERLOADED\u002FUNBALANCED).\n3. **12-month quarterly hiring plan** accounting for ramp curves,\n   attrition, QoQ demand growth, and span-of-control manager triggers.\n\n## When to use\n\n- **Annual ops capacity planning** (October-November for the following\n  fiscal year).\n- **Quarterly re-sizing** if demand changed >15% or attrition spiked.\n- **Pre-budget defense** — the math that justifies the headcount ask\n  to your CFO.\n- **Diagnostic** when an ops team is missing SLA and you need to know\n  whether it's a sizing problem, a process problem, or a bottleneck\n  problem.\n- **M&A \u002F new-segment launch** modeling — sizing a new team or\n  combined org.\n\n## Workflow\n\n1. **Intake demand**. Pull P50\u002FP90\u002FP99 daily ticket\u002Fcase volume from\n   your work system (Zendesk, Intercom, JSM, ServiceNow, Salesforce).\n   If you only have averages, stop and pull the distribution. Single-\n   point demand estimates are the most expensive anti-pattern in ops.\n2. **Model throughput**. Run `capacity_modeler.py` with your demand,\n   AHT, SLA target, current FTE, and shrinkage. Use `--profile` for\n   your function (support \u002F cx \u002F bizops \u002F finance-ops \u002F it-ops). Read\n   the 80%-utilization row — that's your sizing point.\n3. **Flag utilization risk**. Run `utilization_analyzer.py` against\n   your current team's actual utilization data. Anyone >85% sustained\n   is a throughput-collapse risk per Reinertsen. Spread >30 percentage\n   points across team means UNBALANCED — fix that before hiring.\n4. **Sequence hiring**. Run `hiring_sequencer.py` with current FTE,\n   target EOY, ramp time, attrition, and growth. It will front-load\n   hires (Q1 35%, Q4 15%), apply ramp curves, and trigger a manager\n   hire when span of control crosses 7 ICs\u002Fmanager.\n5. **Walk the Forcing-question library** (see below). One question at\n   a time. Do not skip ahead. Answers must be written down before\n   you commit the plan.\n\n## Scripts\n\n- `scripts\u002Fcapacity_modeler.py` — Erlang-C sizing with shrinkage\n  adjustment and P50\u002FP90\u002FP99 breach probabilities. `--profile`\n  for industry defaults.\n- `scripts\u002Futilization_analyzer.py` — per-member traffic-light +\n  team-level health verdict with variance detection.\n- `scripts\u002Fhiring_sequencer.py` — 12-month quarterly plan with ramp,\n  attrition, growth, max-hires-per-quarter constraint, and\n  manager-trigger logic.\n\nAll three accept `--input \u003Cpath>` (JSON), `--output {markdown,json}`,\n`--sample` (built-in example), and `--help`. Stdlib only.\n\n## References\n\n- `references\u002Fqueueing_theory_canon.md` — Erlang, Little, Hopp &\n  Spearman, Reinertsen, Kingman, Cleveland, ITIL, Armony et al. (8\n  sources). The math.\n- `references\u002Fops_workforce_planning_canon.md` — Fournier, Larson,\n  Google SRE Workbook, Frei, Lawler, Bersin, Gartner, Grove (8\n  sources). The people factors.\n- `references\u002Fcapacity_anti_patterns.md` — 11 named anti-patterns\n  with cited sources, tool guards, and the meta-discipline that\n  Lencioni + Goldratt + Christensen impose. (8+ named sources.)\n\n## Assets\n\n- `assets\u002Fcapacity_brief_template.md` — 20-minute fill-out template\n  with JSON skeletons for all three tools and an output checklist.\n\n## Assumptions\n\nThis skill assumes:\n\n- Work is **queued** (tickets, cases, work items) — not project-style.\n  If your team's work isn't queued, this is the wrong skill.\n- Demand has a **stationary-enough distribution** within a quarter.\n  Step-changes (new product launch, M&A, regulatory shift) require\n  re-running mid-quarter.\n- You have **at least 90 days of historical demand data** to compute\n  P50\u002FP90\u002FP99. If not, generate the distribution from your sales \u002F\n  user-base forecast first.\n- Service is **single-class** within a queue. If you have hard\n  priority tiers (P1\u002FP2\u002FP3 with class-specific SLAs), model each as\n  a separate queue and sum.\n- **Channels are modeled coherently.** Multi-channel teams use the\n  appropriate `--profile` with built-in shrinkage premium.\n\n## Anti-patterns\n\nSee `references\u002Fcapacity_anti_patterns.md` for the full taxonomy with\nsources. Top eight:\n\n1. Plan-to-100%-utilization (Reinertsen Principle 12)\n2. Treat-ramp-as-instant (Larson)\n3. Ignore-attrition-in-12-month-plan (Bersin)\n4. Hire-ICs-forever-with-no-manager-trigger (Fournier)\n5. Size-to-P50-demand-only (Cleveland)\n6. No-shrinkage-adjustment (Cleveland, SRE Workbook)\n7. Single-channel-model-for-multi-channel-work (Gartner, Kingman)\n8. No-surge-plan-for-P99-events (Hopp & Spearman, Reinertsen)\n\n## Distinct from\n\n- **`c-level-advisor\u002Fvpe-advisor`** measures *engineering* throughput\n  via DORA 4 metrics, story points, deployment frequency, and cycle\n  time bottlenecks. It is for engineering teams shipping code. This\n  skill is for ops teams handling tickets\u002Fcases. Different unit of\n  work, different math (Erlang-C vs. DORA), different bottleneck\n  (queueing-blind staffing vs. WIP + lead time).\n- **`c-level-advisor\u002Fchro-advisor`** does *strategic* workforce\n  planning (1-5 year capability portfolios, talent supply, leadership\n  succession). This skill does *operational* 0-12 month capacity\n  sizing against demand. Per Lawler: conflating them gets you hired\n  into the wrong jobs.\n- **`project-management\u002F*`** tracks delivery throughput on projects\n  (Jira velocity, sprint capacity). This skill sizes around steady-\n  state queued work.\n- **Sibling `process-mapper`** *finds* the bottleneck. This skill\n  *sizes the team around* a known bottleneck. Order of operations:\n  process-mapper first → capacity-planner second. Hiring around the\n  wrong constraint wastes the hires.\n- **`business-growth\u002Fcs-coverage`** (if it exists) sizes Customer\n  Success coverage by ARR\u002FCSM ratio and segment. This skill sizes by\n  queued work volume (tickets, cases, escalations). For a CS team\n  that handles both relationship work AND a ticket queue, run both.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\n**Discipline**: walk these one at a time. Do not skip ahead. Answers must\nbe written down. If you can't answer one, that is your next investigation.\n\n### Q1 — \"What is your bottleneck, and have you confirmed it empirically?\"\n\n**Recommended answer**: a named, measured stage in the workflow with\nqueue-time data showing where work waits. Not a vibe. Not \"escalations\ntake too long\". An actual measured queue.\n\n**Why it's the first question**: Goldratt (*The Goal*, 1984) — every\nsystem has exactly one binding constraint at a time. Sizing around the\nwrong constraint wastes hires entirely. If you do not know your\nbottleneck, run `process-mapper` BEFORE this skill.\n\n**Canon**: Eli Goldratt, *The Goal* (1984); Reinertsen, *Principles of\nProduct Development Flow* (2009).\n\n### Q2 — \"What service trade-off are you accepting?\"\n\n**Recommended answer**: a written, explicit choice — fast vs. empathetic,\nbroad vs. deep, low-cost vs. high-quality. Frances Frei is unambiguous:\nyou cannot win all four. The team that tries wins zero.\n\n**Why it matters**: AHT, SLA, and shrinkage inputs are the operational\nexpression of this trade-off. If they don't agree (e.g., you set AHT for\n\"empathy\" but SLA for \"speed\"), the plan is internally inconsistent.\n\n**Canon**: Frances Frei & Anne Morriss, *Uncommon Service* (HBR Press,\n2012).\n\n### Q3 — \"What's your demand P90, and what's the gap to your P99?\"\n\n**Recommended answer**: two specific numbers from the last 90 days of\ndata, with the calendar context of each (e.g., \"P90 was 480 tickets\u002Fday\non normal Tuesdays; P99 was 720 on the day after the November release\").\nA team sized to P50 misses SLA half the time. A team sized to P99\noverstaffs by 30-50%. P90 is the right operating sizing point per\nCleveland.\n\n**Canon**: Brad Cleveland, *Call Center Management on Fast Forward* (4th\ned., 2019); A.K. Erlang, *The Theory of Probabilities and Telephone\nConversations* (1909).\n\n### Q4 — \"At your planned utilization, what is P(SLA breach) at P90 and at P99?\"\n\n**Recommended answer**: two probabilities, computed (not guessed) from\nErlang-C with your specific N, AHT, and SLA target. If P(breach at P90)\n> 10% you are understaffed at the sizing point. If P(breach at P99) >\n50% you have no surge plan and the next peak event will be visible to\nthe CEO.\n\n**Canon**: Erlang (1909); Hopp & Spearman, *Factory Physics* (3rd ed.,\n2008), VUT equation.\n\n### Q5 — \"Have you budgeted replacement hires for the attrition you'll see this year?\"\n\n**Recommended answer**: yes, with a specific number. At 30% annual\nattrition (Bersin BPO midpoint), a 20-FTE team loses ~6 people this year.\nIf your \"add 5 net\" plan is actually a \"hire 11\" plan, the recruiting\nvolume changes drastically. Anti-pattern #3.\n\n**Canon**: Bersin\u002FDeloitte talent benchmarks (2015-2023); Edward Lawler,\n*Strategic Workforce Planning* (USC CEO, 2008).\n\n### Q6 — \"When does span of control trigger a manager hire, and who is the candidate?\"\n\n**Recommended answer**: a specific quarter (from `hiring_sequencer.py`)\nand at least one identified candidate (internal lead or external hire).\nPast 7 ICs\u002Fmanager, 1:1s degrade, feedback cycles slip, attrition\nclimbs. Past 10 you have a coverage crisis. Hire the manager BEFORE\ncrossing 10, not after.\n\n**Canon**: Camille Fournier, *The Manager's Path* (O'Reilly, 2017),\nch. 5; Andy Grove, *High Output Management* (1983).\n\n### Q7 — \"What is your surge plan for the P99 day?\"\n\n**Recommended answer**: an explicit, documented plan — overflow tier,\nBPO contracted capacity, on-call rotation, executive escalation tree,\nOR a written degradation contract that says \"on P99 days we extend SLA\nto X minutes and notify customers proactively\". If the answer is \"we'll\nfigure it out\", the P99 day is a fire visible to the board.\n\n**Canon**: Hopp & Spearman, *Factory Physics* (2008); Reinertsen (2009)\non capacity-margin discipline.\n\n---\n\n**Walk these seven in order. One at a time. Write the answers down. The\nplan you submit is only as defensible as your answers to these seven\nquestions.**\n",{"name":5,"tags":23,"author":32,"license":14,"version":33,"description":7,"compatible_tools":34},[24,25,26,27,28,29,30,31],"bizops","capacity","headcount","utilization","queueing-theory","ops-planning","little-law","workforce","claude-code-skills","2.8.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add ASoudy\u002FAGS --skill capacity-planner",{"tool":53,"command":54},"bunx","bunx skills add ASoudy\u002FAGS --skill capacity-planner",{"tool":56,"command":57},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill capacity-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002FSKILL.md",true,[61,67,73,77,81,87,91],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Fcapacity_brief_template.md","ASSET","资产文件",4984,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Fassets\u002Fcapacity_brief_template.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcapacity_anti_patterns.md","REFERENCE","参考文档",9049,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Freferences\u002Fcapacity_anti_patterns.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fops_workforce_planning_canon.md",6317,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Freferences\u002Fops_workforce_planning_canon.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fqueueing_theory_canon.md",5981,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Freferences\u002Fqueueing_theory_canon.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fcapacity_modeler.py","SCRIPT","脚本",16385,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Fscripts\u002Fcapacity_modeler.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fhiring_sequencer.py",12501,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Fscripts\u002Fhiring_sequencer.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Futilization_analyzer.py",9906,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fcapacity-planner\u002Fscripts\u002Futilization_analyzer.py",[96,103,110,117,124,131],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]