메뉴
"Use when forecasting team capacity, planning quarterly work, or deciding what to cut. Triggers on "capacity", "forecast", "roadmap", "can we ship it", "headcount", "planning"."
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | Capacity Model |
| description | "Use when forecasting team capacity, planning quarterly work, or deciding what to cut. Triggers on "capacity", "forecast", "roadmap", "can we ship it", "headcount", "planning"." |
Available capacity = headcount x working days x focus factor
Typical focus factors:
Subtract: PTO, public holidays, known leaves, training.
10 people x 65 working days = 650 person-days
- 12 days PTO average per person = -120 days
- On-call overhead (2 people/week x 13 weeks x 1 day) = -26 days
- Hiring interviews (2 loads x 8 panellists x 2h) = -4 days
= 500 raw days
x 0.65 average focus factor = 325 focused person-days
Reserve 20% for unknowns = 260 planned person-days
## Q<N> Capacity Plan
| Metric | Value |
|---|---|
| Raw person-days | 650 |
| After leave/overhead | 500 |
| Focused (x0.65) | 325 |
| Planned (x0.80) | 260 |
**Demand**: 290 person-days estimated
**Gap**: -30 person-days -> cut or defer
### Cut list
1. Feature X (P2, 40d) -> defer to Q<N+1>
2. Tech debt initiative Y (80d) -> reduce to first phase only (30d)
Every quarterly plan must show demand, supply, and gap - never only a feature list.
"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."
"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."
"Use when drafting Architecture Decision Records, evaluating alternatives, or documenting technical trade-offs. Triggers on "ADR", "architecture decision", "trade-off", "pick between", "why did we choose"."
"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."
Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.
Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.