Purpose
Produce a defensible, domain-by-domain assessment of where a workforce's digital capabilities fall short of what the strategy requires — and translate each gap into a specific hire, reskill, or outsource decision with cost and timeline implications. Replaces gut-feel headcount debates with a structured capability map executives can fund and act on.
When to Use
Invoke this skill when the user asks to:
- Assess digital capability or skills gaps across the workforce
- Decide whether to hire, reskill, or outsource for a digital initiative
- Build a talent strategy for a digital transformation program
- Justify a reskilling or upskilling investment to the board or CEO
- Benchmark current digital maturity against target-state requirements
- Prioritize which capability gaps to close first given a fixed budget
Inputs Required
Before starting, collect:
- Strategic digital priorities: The 3–5 business outcomes driving the need (e.g., migrate to cloud, launch a data platform, build in-house product teams)
- Target digital domains: Which capabilities matter — from data science, cloud engineering, UX/design, product management, cybersecurity, and adjacent areas
- Workforce baseline: Current headcount by relevant function, and any known skill inventory, certification, or assessment data
- Time horizon: When target-state capability must be in place (e.g., 12 / 24 / 36 months)
- Budget posture: Rough constraint — cost-constrained, balanced, or speed-prioritized
- Constraints: Hiring market difficulty, geographic limits, retention risk, or union/policy factors
- Current sourcing mix: Any existing use of contractors, agencies, or managed services
If a formal skill inventory is unavailable, proceed with role-level proxies (job families, seniority bands) and flag the assessment as directional pending validation.
Instructions
Step 1: Define the Target-State Capability Map
For each target domain, break the capability into a proficiency ladder using a recognized taxonomy structure (e.g., SFIA levels or the EU DigComp / e-Competence Framework). Specify:
- Sub-capabilities required (e.g., Data Science → data engineering, ML modeling, MLOps, analytics translation)
- Proficiency level required per sub-capability on a 4-tier scale: Awareness / Working / Practitioner / Expert
- Headcount required at each level to deliver the strategic priorities
- Criticality: Mission-critical / Important / Supporting — based on link to the priorities in Step 1's inputs
Step 2: Assess Current-State Capability
For each sub-capability, estimate the current workforce position:
- Current headcount at each proficiency tier (from inventory data or role-level proxy)
- Confidence level of the estimate (High if assessment-backed; Low if role-proxy only)
- Concentration risk: Flag any capability held by 1–2 individuals ("bus factor")
- Trajectory: Is this capability growing, static, or eroding (attrition, retirement, obsolescence)?
Step 3: Quantify the Gaps
For each sub-capability, compute and classify the gap:
- Gap size: Required minus current headcount at the required proficiency tier
- Gap severity using a two-axis rating — criticality (from Step 1) × gap size:
- Red / Critical: Mission-critical capability with a material headcount shortfall
- Amber / Watch: Important capability with a moderate shortfall, or a critical one nearly met
- Green / Covered: Adequate or minor gap
- Rank all Red gaps into a single prioritized list — this drives the strategy.
Step 4: Recommend a Build / Buy / Borrow Strategy Per Gap
For each Red and Amber gap, recommend one primary sourcing route with rationale:
- Build (reskill/upskill) — best when adjacent skills exist internally, the capability is durable and strategic, and the time horizon allows 6–18 months. Specify the source population and the reskilling pathway.
- Buy (hire) — best when no adjacent internal base exists, the capability must be permanent, and the market is accessible. Note expected time-to-fill and market difficulty.
- Borrow (outsource/contract) — best when the need is temporary, specialized, or urgent, or the capability is non-differentiating. Note whether it's a bridge (borrow now, build later) or a permanent managed-service decision. Apply a decision rule: differentiating + durable → Build; differentiating + urgent → Buy; non-differentiating or temporary → Borrow.
Step 5: Build the Phased Roadmap
Sequence the closure of gaps over the time horizon in three waves:
- Wave 1 (0–6 months): Address Red gaps that are unblocking — hire critical roles, stand up borrow arrangements, launch first reskilling cohort
- Wave 2 (6–18 months): Reskilling programs mature, second-wave hires, convert bridge-borrows toward build
- Wave 3 (18+ months): Steady-state capability, retire outsourcing where build succeeded, embed continuous learning For each wave, state the actions, owners, and the capability milestone that marks success.
Step 6: Estimate Investment and Risk
- Cost ranges per route: reskilling cost per person, expected fully-loaded hire cost, contractor/managed-service run-rate — as ranges, clearly labeled as planning estimates
- Key risks: hiring-market failure, reskilling attrition, over-reliance on contractors, concentration risk
- Leading indicators to track quarterly: gaps closed, cohort completion, time-to-fill, internal mobility rate
Output Format
- Structure: Executive summary → target-state capability map (table) → current-state assessment → prioritized gap register (table) → build/buy/borrow recommendations → phased roadmap → investment & risk
- Length: 1,100–1,500 words
- Format: Structured document with two supporting tables (capability map; gap register with severity rating)
- Sections: Executive Summary, Target-State Capability Map, Current-State Assessment, Prioritized Gap Register, Build/Buy/Borrow Strategy, Phased Roadmap, Investment & Risk
- Tone: Chief people/digital officer briefing the board — analytical, decisive, cost-aware, no jargon inflation
Quality Checklist
Before delivering output, verify:
- [ ] Every target domain is broken into named sub-capabilities with a required proficiency tier and headcount
- [ ] Each gap carries a severity rating derived from criticality × gap size — not a single arbitrary label
- [ ] The gap register is ranked, with Red gaps at the top
- [ ] Every Red and Amber gap has exactly one primary sourcing recommendation with a stated rationale
- [ ] The roadmap sequences actions across three time-bound waves with a milestone per wave
- [ ] Cost figures are presented as labeled planning ranges, not false-precision point estimates
Notes
- Reskilling is systematically underused because it's slow to feel and hard to measure — but for durable, differentiating capabilities it is almost always cheaper and more retentive than repeated external hiring. Bias toward Build for the core, Borrow for the edges.
- The single most valuable output is often the concentration-risk flag: capabilities held by one person represent silent strategic exposure regardless of headline gap size.
- When workforce data is role-proxy only, state the confidence level explicitly and recommend a lightweight skills assessment as the first roadmap action — a wrong baseline invalidates the whole strategy.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills