Hr Demand Planning logo

Hr Demand Planning

Community
tuanductran
hr-demand-planning

Help HR leaders, workforce planners, and TA teams translate business strategy into headcount demand plans. Use when asked to build a headcount plan, forecast short-term hiring demand, model workforce demand, align HR capacity with business growth, create a staffing demand forecast, or plan headcount for [department or product launch].

Overview

Publishertuanductran
Repositoryhr-skills
Skill namehr-demand-planning
Stars
78
Forks
20
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by tuanductran on GitHub. Read the source before you install it.

Installation

Install the Hr Demand Planning AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/tuanductran/hr-skills/tree/main/skills/hr-demand-planning
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tuanductran/hr-skills.git /tmp/hr-skills
mkdir -p .claude/skills
cp -r /tmp/hr-skills/skills/hr-demand-planning .claude/skills/hr-demand-planning
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hr Demand Planning in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hr Demand Planning on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hr Demand Planning is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

HR demand planning

Translate business strategy and operational plans into accurate headcount demand forecasts — from gathering demand signals and modeling capacity requirements to prioritizing critical roles and aligning recruiting resources.

Supported tasks

  • Translating business plans into headcount demand models
  • Gathering and validating demand signals from business leaders
  • Modeling headcount requirements by role, level, and location
  • Prioritizing critical hires against available recruiting capacity
  • Designing demand intake and approval processes
  • Building rolling demand forecasts with scenario modeling
  • Aligning demand plans with budget and span-of-control targets
  • Identifying demand volatility patterns and mitigation strategies
  • Reporting demand vs. supply gaps to TA and HRBP partners
  • Designing workforce demand review cadences with business stakeholders
  • Connecting demand plans to recruiting pipeline and sourcing strategy

Key prompts

Demand signal gathering

  1. "Design a headcount demand intake process for [company] that gathers accurate signals from business leaders."
  2. "What questions should we ask business leaders to translate product or revenue growth into role-level headcount demand?"
  3. "How do we validate demand signals to avoid inflated headcount requests that drain recruiting capacity?"
  4. "Build a demand intake template for [department or function] that captures role, level, location, start date, and business justification."
  5. "How should HR business partners run quarterly demand planning conversations with their business unit leaders?"

Demand modeling

  1. "Model headcount demand for [department] growing from [current headcount] to [target] over [timeframe]."
  2. "What factors should drive a productivity-based headcount model for [function, for example, sales, engineering, support]?"
  3. "Design a scenario model that shows headcount demand under [conservative / base / aggressive] growth assumptions."
  4. "How do we account for attrition, internal transfers, and backfills when building a net new headcount demand model?"
  5. "What span-of-control ratios should we apply when modeling management headcount demand for [organization size]?"
  6. "How do we model headcount demand for a product launch with uncertain ramp timing?"

Demand prioritization

  1. "How do we prioritize [number] open reqs when TA capacity can only support [number] per quarter?"
  2. "Build a role criticality scoring framework to prioritize demand when supply is constrained."
  3. "What criteria should a hiring committee use to decide which roles to defer versus accelerate in a slow-hiring quarter?"
  4. "How do we communicate demand prioritization decisions back to business leaders in a way they find credible?"

Demand and supply alignment

  1. "Compare our current hiring demand plan against TA capacity and identify where gaps will occur in [quarter]."
  2. "How do we translate a demand plan into sourcing channel requirements and recruiter workload projections?"
  3. "Design a weekly demand vs. supply review process for [TA team / HRBP team]."
  4. "What early warning metrics tell us demand is outpacing our TA supply chain before the pipeline dries up?"
  5. "How should we adjust our demand plan when business strategy changes mid-year?"

Reporting and governance

  1. "Build a monthly headcount demand report for [CHRO / CFO / business leadership] showing demand, approved positions, and pipeline coverage."
  2. "What governance process ensures demand changes go through proper review before recruiting resources are committed?"
  3. "How do we track demand forecast accuracy and use it to improve planning in future quarters?"
  4. "Design a dashboard that shows demand plan status to business leaders without requiring them to interpret raw HRIS data."

Tips

  • Demand quality matters more than demand quantity — one accurate, well-scoped req is worth more to TA than five vague or rapidly changing ones.
  • Business leaders often conflate "wish list" with "demand" — use business justification gates and budget confirmation steps to surface real versus aspirational need.
  • Build rolling 90-day and 6-month demand horizons; annual plans become stale quickly in high-growth or volatile environments.
  • Segment demand by criticality (revenue-generating, compliance-critical, backfill, growth) to make prioritization discussions with leadership easier and more defensible.
  • Demand planning accuracy improves significantly when HR partners attend business planning meetings rather than receiving the output after decisions are made.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Hr Demand Planning AI skill do?

Help HR leaders, workforce planners, and TA teams translate business strategy into headcount demand plans. Use when asked to build a headcount plan, forecast short-term hiring demand, model workforce demand, align HR capacity with business growth, create a staffing demand forecast, or plan headcount for [department or product launch].

Why use Hr Demand Planning on TypingMind?

Because you install it once and use it with any model. Hr Demand Planning is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hr Demand Planning in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tuanductran/hr-skills/tree/main/skills/hr-demand-planning. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hr Demand Planning?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hr Demand Planning?

As many as you like. As long as a model supports skills, you can use Hr Demand Planning with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hr Demand Planning AI skill free?

Yes. It is published on GitHub by tuanductran under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇