Turn account load and team capacity data into a resource plan with coverage analysis, at-risk gaps, and reallocation recommendations.
Analyze account load against team capacity to produce a prioritized resource plan identifying coverage gaps, at-risk accounts, and concrete reallocation recommendations.
Invoke when preparing for a planning cycle, after headcount changes, or when team utilization signals imbalance across accounts.
Ingest the raw capacity and account load data below and parse it into two structured lists: (1) each team member with their current account assignments and estimated weekly hours committed, and (2) each account with its tier, complexity, and required coverage hours. $capacity_and_load_data
Analyze the resource data below:
$capacity_and_load_dataCalculate utilization for each team member as a percentage of their available weekly capacity. Flag anyone below 70% (underutilized) or above 90% (overloaded). Summarize the team's aggregate utilization rate.
Identify at-risk coverage gaps: accounts whose required hours exceed what their assigned owner can realistically deliver, accounts with no backup owner, and high-tier accounts held by overloaded team members. Rank gaps by business risk (account tier × coverage shortfall).
Generate a reallocation recommendation table. For each at-risk gap, propose a specific move: which account or task to shift, from whom, to whom, and the estimated hours relieved. Prioritize moves that resolve the highest-risk gaps with the least disruption.
Produce an executive summary (5–7 bullet points) covering: current team utilization state, number and severity of coverage gaps, top three reallocation actions, and any accounts that remain at risk even after reallocation due to structural capacity shortfall.
Return four clearly labeled sections: (1) Utilization Breakdown — a table of each team member, committed hours, available hours, and utilization %; (2) At-Risk Gap Register — ranked list of coverage gaps with risk level; (3) Reallocation Recommendation Table — proposed moves with giver, receiver, account, and hours; (4) Executive Summary — 5–7 bullets on overall state and top actions.
Copy this skill into your library to inject it into Claude, ChatGPT, and Gemini — or install your whole library as / slash commands in Claude Code and Cowork.
Get started free →Related skills
Transform raw work logs into a polished, stakeholder-ready weekly status report in minutes.
Generate a clear, inclusive job description from a role title and requirements in seconds.
Draft a blameless postmortem from an incident timeline and impact summary, following SRE best practices.