hr-org-planning

Builds org charts, headcount plans, and hiring sequences with cost projections for team structures.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill hr-org-planning-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hr-org-planning
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/hr-org-planning
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill hr-org-planning-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid under-hiring, mis-structuring teams, and unclear reporting lines by turning org design and headcount decisions into a concrete, sequenced plan.

Core Features & Use Cases

  • Headcount planning and budgeting: Model needed roles, timing, and monthly/annual cost trade-offs to support hiring decisions.
  • Org structure and org chart design: Define spans of control, management layers, and reporting boundaries suitable for small teams.
  • Hiring sequencing and risk identification: Prioritize roles based on bottlenecks, single points of failure, and recurring overload.

Quick Start

Use the skill to generate a headcount plan and suggested org chart for your team by providing your current structure, target timeframe, and the roles you are considering.

Frequently Asked Questions about hr-org-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a headcount plan with hiring sequences and cost projections?

Headcount planning involves modeling needed roles, timing, and cost trade-offs to support hiring decisions. It translates your desired team structure into role-by-role staffing projections, producing a structured table and recommended hiring rounds.

What is the best way to design an org chart for a small team?

Designing an org chart for a small team requires defining spans of control, management layers, and reporting boundaries. This ensures clear reporting lines and prevents mis-structuring teams by turning organizational design into a concrete plan.

How do I identify organizational risks like bottlenecks and single points of failure?

Identifying organizational risks involves prioritizing roles based on recurring overload, bottlenecks, and single points of failure. This analysis is applied to planned next hires and reorganizations to mitigate structural vulnerabilities within the team.

Can I use this for budget modeling and planning next hires during an org reorganization?

Yes, you can use this for budget modeling and planned next hires during an org reorganization. It supports hiring decisions by modeling monthly and annual cost trade-offs and translating desired structures into sequenced staffing plans.

How do I define span of control and management layers when planning team structure?

Defining span of control and management layers involves setting reporting boundaries suitable for small team contexts. This clarifies reporting lines and translates organizational design decisions into a structured headcount plan.