org-planning

Map headcount needs to roles, reporting lines, and sequencing decisions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sun2443/designer-skills --skill org-planning-sun2443
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: org-planning
Source: https://github.com/sun2443/designer-skills/tree/main/human-resources/skills/org-planning
Command: npx skills add https://github.com/sun2443/designer-skills --skill org-planning-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you make better decisions about team structure, headcount, and org design before you commit to a reorganization or hiring wave.

Core Features & Use Cases

  • Headcount planning: Determine how many people to hire, which roles to add, and by when.
  • Org structure design: Define reporting lines, span of control, and team boundaries to reduce bottlenecks and single points of failure.
  • Sequenced hiring & budget trade-offs: Prioritize hires by criticality and model headcount cost impacts.

Use it when you are planning a reorg, setting targets for next-quarter staffing, or evaluating whether your current structure is too top-heavy or too stretched.

Quick Start

Give the skill your target headcount and current org snapshot, and ask it to produce an org chart plus a sequenced hiring roadmap with cost-aware recommendations.

Frequently Asked Questions about org-planning

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

FAQPage Schema
How do I plan headcount and design an org chart for a reorganization?

Headcount planning and org chart design involve mapping target headcount to specific roles and reporting lines. This defines team boundaries, establishes span of control, and outputs a structured organizational chart alongside sequenced hiring decisions.

What is the best way to sequence hiring and model budget trade-offs?

Sequencing hiring and modeling budget trade-offs requires prioritizing new hires by role criticality. This approach models headcount cost impacts over time, allowing you to evaluate staffing targets and make cost-aware recommendations for next-quarter hiring waves.

How do I know if my team structure is too top-heavy or has excessive management layers?

To determine if a team structure is too top-heavy, evaluate span of control and reporting line depth. Org design reviews flag structural risks like excessive management layers and inefficient spans of control, identifying bottlenecks and single points of failure.

Can I use this for next-quarter staffing targets and budget modeling?

Yes, you can use this for next-quarter staffing targets and budget modeling. By providing a target headcount and current org snapshot, it generates a sequenced hiring roadmap with cost-aware recommendations and headcount cost impact analysis.

What do I need to start mapping organizational structure and reporting lines?

To start mapping organizational structure, you need your target headcount numbers and a snapshot of your current org. Providing these inputs allows the system to produce an org chart, sequenced hiring plan, and cost modeling outputs.