Use when analyzing staffing needs, assessing role requirements, planning agent capacity, or creating staffing templates for multi-agent orchestration. Trigger with team sizing or staffing requests.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-chief-of-staffThis skill uses the workspace's default tool permissions.
Staff planning is a core responsibility of the Chief of Staff agent. It involves analyzing project requirements, assessing available agent capabilities, planning capacity allocation, and creating staffing templates that ensure efficient multi-agent orchestration. This skill teaches you how to perform comprehensive staffing analysis and planning.
Decomposes complex goals into agent team blueprints using scaling laws, topology selection (pipeline, parallel, coordinator, hierarchical), and role design with artifact chains and quality gates. For project planning and team assembly.
Provides best practices for Agent Teams skills: sub-agent setup, SendMessage protocols, task dependencies, logging hooks, context design, and patterns from 7 examples. Use to create new team skills, audit existing, debug communication.
Routes legacy agent-team invocations to dedicated skills for task orchestration, inspection, splitting, workflow governance, worker dispatch, and project bootstrap. For backward compatibility.
Share bugs, ideas, or general feedback.
Staff planning is a core responsibility of the Chief of Staff agent. It involves analyzing project requirements, assessing available agent capabilities, planning capacity allocation, and creating staffing templates that ensure efficient multi-agent orchestration. This skill teaches you how to perform comprehensive staffing analysis and planning.
Before using this skill, ensure:
| Analysis Type | Output |
|---|---|
| Task analysis | Required skills, estimated effort |
| Team sizing | Recommended agent count by role |
| Resource check | Availability vs requirements |
Staff planning is the process of determining which agents are needed, when they are needed, and how they should be allocated across projects and tasks. Unlike simple task assignment, staff planning considers:
Evaluating what agent roles are required for a project or task set:
Determining how much work agents can handle:
Reusable configurations for common scenarios:
When to use: At project start, when adding new features, or when task patterns change.
Steps: Analyze project requirements, list required capabilities, map to agent types, identify gaps.
Related documentation:
When to use: When scheduling work, handling resource conflicts, or optimizing throughput.
Steps: Inventory available agents, estimate task requirements, calculate allocation, identify bottlenecks.
Related documentation:
When to use: When establishing repeatable staffing patterns or standardizing team compositions.
Steps: Identify common scenario, list required roles, define agent assignments, document template.
Related documentation:
These operational runbooks provide step-by-step instructions for executing each staff planning procedure. Use them as quick-reference guides when performing the corresponding operation.
Runbook for analyzing project requirements, extracting required capabilities, mapping them to agent types, performing gap analysis, and creating staffing recommendations.
Runbook for creating agent inventories, estimating task requirements, calculating task allocation, identifying bottlenecks, and recommending mitigations.
Runbook for building reusable staffing configurations for common scenarios like project bootstrap, feature development, bug triage, and release preparation.
Copy this checklist and track your progress:
## Role Assessment: User Authentication Feature
### Required Capabilities
1. Python backend development
2. API design and implementation
3. Security best practices
4. Unit test creation
5. Integration test creation
6. Documentation writing
### Agent Type Mapping
| Capability | Agent Type | Priority |
|------------|------------|----------|
| Backend development | code-implementer | HIGH |
| API design | architect-agent | HIGH |
| Security practices | security-reviewer | MEDIUM |
| Unit tests | test-engineer | HIGH |
| Integration tests | test-engineer | MEDIUM |
| Documentation | doc-writer | LOW |
### Gap Analysis
- No security-reviewer agent available
- Mitigation: code-implementer will follow security checklist
## Capacity Plan: Sprint 42
### Available Agents
- code-implementer: 2 instances
- test-engineer: 1 instance
- doc-writer: 1 instance
### Task Allocation
| Task | Agent | Duration | Parallel |
|------|-------|----------|----------|
| Auth module | code-impl-1 | 4h | Yes |
| User profile | code-impl-2 | 3h | Yes |
| Auth tests | test-eng | 2h | After auth |
| API docs | doc-writer | 1h | After auth |
### Bottleneck
- test-engineer is single instance
- All test tasks must serialize through it
Symptoms: Role assessment shows gaps, tasks remain unassigned.
See references/role-assessment.md Section 1.7 Troubleshooting for resolution.
Symptoms: Tasks queue indefinitely, context windows exhausted.
See references/capacity-planning.md Section 2.7 Troubleshooting for resolution.
Symptoms: Template roles do not match requirements, assignments incorrect.
See references/staffing-templates.md Section 3.7 Troubleshooting for resolution.
See references/role-assessment.md for complete role analysis procedures.
See references/capacity-planning.md for capacity calculation methods.
See references/staffing-templates.md for template creation and usage.
Version: 1.0 Last Updated: 2025-02-01 Target Audience: Chief of Staff Agents Difficulty Level: Intermediate