Skip to content This library is free, offered as dana. If it helps your work, donate here →

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Talent gap identifier

Translates a strategic business plan and current skills inventory into a prioritized capability gap map, scoring each gap by business impact and time-to-criticality, then recommending a build/buy/borrow/automate…

download .md

Purpose

Convert a strategic plan into the specific capabilities the organization must have — then diagnose which of those capabilities are missing, weak, or concentrated in too few people, and recommend the fastest, most cost-effective way to close each gap. Replaces gut-feel hiring plans with a defensible capability roadmap that ties every talent investment to a strategic outcome.

When to Use

Invoke this skill when the user asks to:

  • Identify the capability or skills gaps standing between the current workforce and the strategic plan
  • Build a talent or capability roadmap tied to a growth, transformation, or expansion strategy
  • Decide whether to hire, train, contract, or automate to close a specific skills gap
  • Prioritize workforce investments across competing capability needs with a fixed budget
  • Assess whether the organization has the talent to execute a new product line, market entry, or operating model
  • Prepare a capability-building case for the executive team or board

Inputs Required

Before starting, collect:

  • Strategic plan: The business strategy, growth targets, or transformation initiatives for the next 1–3 years
  • Current skills inventory: Existing roles, headcount, and known skill strengths — org chart, capability matrix, or narrative description
  • Time horizon: When each strategic initiative must be operational (e.g., new market live by Q3)
  • Budget or headcount constraints: Approximate talent budget, hiring freeze status, or headcount cap
  • Non-negotiable capabilities: Any skills that must be built in-house for regulatory, IP, or strategic-control reasons
  • Bench and mobility signals: Known flight risks, single points of failure, or high-potential employees ready to grow
  • Labor market context: Roles known to be scarce, expensive, or hard to hire in the relevant geography

If time horizon or budget is missing, assume a 24-month horizon with moderate budget flexibility and flag the assumption.

Instructions

Step 1: Derive Required Capabilities From Strategy

Break each strategic initiative into the capabilities it demands.

  • For every initiative in the plan, name the 2–4 distinct capabilities required to execute it (e.g., "enter EU market" → regulatory affairs, localization/GTM, multilingual support, data-residency engineering)
  • Distinguish capabilities (durable competencies the org needs) from roles (jobs that deliver them) — one capability may span several roles
  • Tag each capability by type: technical, leadership, commercial, operational, or regulatory/compliance
  • Produce a clean list of 8–15 required capabilities before assessing gaps

Step 2: Assess Current State Against Each Capability

Score the existing workforce on each required capability using a 4-level scale:

  • Strong — depth and redundancy exist; no gap
  • Adequate — present but thin, or concentrated in 1–2 people (concentration risk)
  • Emerging — some foundational skill, needs significant development
  • Absent — capability does not exist in the current workforce

For each capability, note the source of the rating from the inventory (which roles/people cover it) and flag single points of failure where a critical capability sits with one individual.

Step 3: Score and Prioritize Each Gap

For every Adequate/Emerging/Absent capability, score two dimensions on a 1–5 scale:

  • Business Impact: How central is this capability to executing the strategy and hitting the targets? (5 = strategy fails without it)
  • Time-to-Criticality: How soon must it be in place? (5 = needed within the next two quarters)

Compute a Priority Score = Business Impact × Time-to-Criticality (range 1–25) and sort gaps into tiers:

  • Tier 1 — Critical (score 16–25): Close immediately; strategy is at risk
  • Tier 2 — Important (score 9–15): Plan and fund within this horizon
  • Tier 3 — Monitor (score 1–8): Watch; act only if conditions change

Step 4: Recommend a Closure Strategy Per Gap

For each Tier 1 and Tier 2 gap, evaluate all four options and recommend one primary path:

  • Build — develop internal talent via training, stretch assignments, or upskilling. Best when the capability is strategic, must stay in-house, and the time horizon allows development
  • Buy — hire externally. Best when the capability is absent, needed fast, and available in the labor market. Note the market difficulty and lead time
  • Borrow — contractors, fractional leaders, agencies, or partners. Best when the need is temporary, uncertain, or requires expertise too expensive to hire full-time
  • Automate — tooling, AI, or process redesign that reduces or removes the human requirement. Best when the work is repeatable and the capability is operational rather than judgment-heavy

For each recommendation, state the rationale, an estimated speed to close (weeks/months), a relative cost (Low/Medium/High), and the key risk of the chosen path.

Step 5: Sequence the Roadmap

Order the closure moves across the time horizon:

  • Front-load Tier 1 gaps and any capability that is a prerequisite for others
  • Flag dependencies (e.g., a leader must be hired before a team can be built beneath them)
  • Balance the portfolio against the stated budget/headcount constraint — if constrained, recommend which Tier 2 gaps to defer and why
  • Identify quick wins (gaps closable in under 90 days) versus multi-quarter builds

Step 6: Summarize the Executive Case

Deliver a one-paragraph summary a CHRO can bring to the executive team: the number of critical gaps, the top three that most threaten the strategy, the recommended mix of build/buy/borrow/automate, and the headline investment implication.

Output Format

  • Structure: Required capabilities list → current-state assessment → prioritized gap table → per-gap closure recommendations → sequenced roadmap → executive summary
  • Length: 1,000–1,400 words
  • Format: Structured document with a central gap-prioritization table (Capability | Current State | Impact | Time-to-Criticality | Priority Score | Tier | Recommended Path); closure recommendations as structured bullets per gap
  • Sections: Required Capabilities → Current-State Assessment → Prioritized Gap Map → Closure Strategy by Gap → Sequenced Roadmap → Executive Summary
  • Tone: Talent strategy director — analytical, decisive, and tied to business outcomes rather than HR abstractions

Quality Checklist

Before delivering output, verify:

  • [ ] Every required capability traces back to a specific strategic initiative — none are generic HR wishlist items
  • [ ] Each gap has both an Impact score and a Time-to-Criticality score, with the Priority Score calculated and tiered
  • [ ] Every Tier 1 and Tier 2 gap has one recommended path (build/buy/borrow/automate) with rationale, speed, cost, and risk
  • [ ] Single points of failure and concentration risks are explicitly flagged in the current-state assessment
  • [ ] The roadmap respects the stated budget/headcount constraint and names any deferred gaps
  • [ ] The executive summary names the top three strategy-threatening gaps specifically

Notes

  • The most common error is confusing roles with capabilities — always decompose to the durable competency, since one hire rarely closes an entire capability gap
  • "Adequate but concentrated in one person" is a hidden gap that often outranks visibly absent capabilities on risk — treat single points of failure as Tier 1 candidates even when nominally staffed
  • Default to Borrow for capabilities whose future demand is uncertain; committing to Build or Buy prematurely locks in fixed cost against an unproven need
  • When budget is tight, automating an operational capability often frees the headcount needed to Build a strategic one — surface these trade-offs explicitly in the roadmap

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:

  1. Drag this file into a new chat, or copy and paste its contents
  2. 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