Define requirements for an OpenClaw integration
Document a proposed integration's data needs, actions, credentials, and review boundaries.
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.
--- name: org-planning-b3c6e33d2514 description: 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. --- # Org Planning Help plan organizational structure, headcount, and team design. ## Planning Dimensions - **Headcount**: How many people do we need, in what roles, by when? - **Structure**: Reporting lines, span of control, team boundaries - **Sequencing**: Which hires are most critical? What's the right order? - **Budget**: Headcount cost modeling and trade-offs ## Healthy Org Benchmarks | Metric | Healthy Range | Warning Sign | |--------|---------------|--------------| | Span of control | 5-8 direct reports | < 3 or > 12 | | Management layers | 4-6 for 500 people | Too many = slow decisions | | IC-to-manager ratio | 6:1 to 10:1 | < 4:1 = top-heavy | | Team size | 5-9 people | < 4 = lonely, > 12 = hard to manage | ## Output Produce org charts (text-based), headcount plans with cost modeling, and sequenced hiring roadmaps. Flag structural issues like single points of failure or excessive management overhead.--- name: org-planning-b3c6e33d2514 description: 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. --- # Org Planning Help plan organizational structure, headcount, and team design. ## Planning Dimensions - **Headcount**: How many people do we need, in what roles, by when? - **Structure**: Reporting lines, span of control, team boundaries - **Sequencing**: Which hires are most critical? What's the right order? - **Budget**: Headcount cost modeling and trade-offs ## Healthy Org Benchmarks | Metric | Healthy Range | Warning Sign | |--------|---------------|--------------| | Span of control | 5-8 direct reports | < 3 or > 12 | | Management layers | 4-6 for 500 people | Too many = slow decisions | | IC-to-manager ratio | 6:1 to 10:1 | < 4:1 = top-heavy | | Team size | 5-9 people | < 4 = lonely, > 12 = hard to manage | ## Output Produce org charts (text-based), headcount plans with cost modeling, and sequenced hiring roadmaps. Flag structural issues like single points of failure or excessive management overhead.
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.