LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

org-planning

Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.

22,223stars2,604forksUpdated 7/1/2026
Developer Tools#org-design#team-structure#management#budgeting#headcount-planning

Security Assessment

Safe(100/100)
Security Score100/100

About org-planning

Org Planning helps plan organizational structure, headcount, and team design. It is triggered by phrases such as "org planning," "headcount plan," "team structure," "reorg," or "who should we hire next," and more generally when someone is thinking about team size, reporting structure, or organizational design. The skill frames the problem across four planning dimensions: headcount (how many people are needed, in what roles, and by when), structure (reporting lines, span of control, and team boundaries), sequencing (which hires are most critical and in what order), and budget (headcount cost modeling and trade-offs).

To ground recommendations, the skill provides a set of healthy org benchmarks with explicit ranges and warning signs. A span of control of five to eight direct reports is considered healthy, while fewer than three or more than twelve is a warning sign. It suggests four to six management layers for an organization of 500 people, cautioning that too many layers slow decisions. An IC-to-manager ratio between 6:1 and 10:1 is healthy, with below 4:1 indicating a top-heavy structure. Team size of five to nine people is the target, noting that fewer than four can feel lonely and more than twelve is hard to manage.

As output, the skill produces text-based org charts, headcount plans with cost modeling, and sequenced hiring roadmaps. It also flags structural issues, such as single points of failure or excessive management overhead, so leaders can address risks in the proposed structure. The documentation is concise and high level, positioning the skill as a planning aid for decisions about how large a team should be, how it should report, and which roles to prioritize next.

FAQ

When should I trigger this skill?

Use it for org planning, headcount plans, team structure, reorgs, or deciding who to hire next—generally whenever you're thinking about team size, reporting structure, or organizational design.

What is considered a healthy span of control?

Five to eight direct reports is the healthy range. Fewer than three or more than twelve is flagged as a warning sign.

What IC-to-manager ratio does it recommend?

A ratio between 6:1 and 10:1 is healthy. Below 4:1 is considered top-heavy.

What outputs does it produce?

It produces text-based org charts, headcount plans with cost modeling, and sequenced hiring roadmaps, and it flags structural issues like single points of failure or excessive management overhead.

How many management layers does it suggest for a larger org?

It suggests four to six management layers for an organization of about 500 people, warning that too many layers slow decisions.

Install org-planning

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

anthropics/knowledge-work-plugins

Related Skills

short-form-video

14

multi-asset-morning-briefing

7,907

content-strategy

2,901

doherty-threshold

2,901