anthropics/knowledge-work-plugins

capacity-plan

Plan resource capacity — workload analysis and utilization forecasting.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill capacity-plan

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

/capacity-plan

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Analyze team capacity and plan resource allocation.

Usage

/capacity-plan $ARGUMENTS

What I Need From You

  • Team size and roles: Who do you have?
  • Current workload: What are they working on? (Upload from project tracker or describe)
  • Upcoming work: What's coming next quarter?
  • Constraints: Budget, hiring timeline, skill requirements

Planning Dimensions

People

  • Available headcount and skills
  • Current allocation and utilization
  • Planned hires and timeline
  • Contractor and vendor capacity

Budget

  • Operating budget by category
  • Project-specific budgets
  • Variance tracking
  • Forecast vs. actual

Time

  • Project timelines and dependencies
  • Critical path analysis
  • Buffer and contingency planning
  • Deadline management

Utilization Targets

Role TypeTarget UtilizationNotes
IC / Specialist75-80%Leave room for reactive work and growth
Manager60-70%Management overhead, meetings, 1:1s
On-call / Support50-60%Interrupt-driven work is unpredictable

Common Pitfalls

  • Planning to 100% utilization (no buffer for surprises)
  • Ignoring meeting load and context-switching costs
  • Not accounting for vacation, holidays, and sick time
  • Treating all hours as equal (creative work ≠ admin work)

Output

markdown
## Capacity Plan: [Team/Project]
**Period:** [Date range] | **Team Size:** [X]

### Current Utilization
| Person/Role | Capacity | Allocated | Available | Utilization |
|-------------|----------|-----------|-----------|-------------|
| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |

### Capacity Summary
- **Total capacity**: [X] hours/week
- **Currently allocated**: [X] hours/week ([X]%)
- **Available**: [X] hours/week ([X]%)
- **Overallocated**: [X people above 100%]

### Upcoming Demand
| Project/Initiative | Start | End | Resources Needed | Gap |
|--------------------|-------|-----|-----------------|-----|
| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |

### Bottlenecks
- [Skill or role that's oversubscribed]
- [Time period with a crunch]

### Recommendations
1. [Hire / Contract / Reprioritize / Delay]
2. [Specific action]

### Scenarios
| Scenario | Outcome |
|----------|---------|
| Do nothing | [What happens] |
| Hire [X] | [What changes] |
| Deprioritize [Y] | [What frees up] |

If Connectors Available

If ~~project tracker is connected:

  • Pull current workload and ticket assignments automatically
  • Show upcoming sprint or quarter commitments per person

If ~~calendar is connected:

  • Factor in PTO, holidays, and recurring meeting load
  • Calculate actual available hours per person

Tips

  1. Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.
  2. Plan for buffer — Target 80% utilization. 100% means no room for surprises.
  3. Update regularly — Capacity plans go stale fast. Review monthly.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
anthropics
Officiel

contract-review

Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal

Installations / 1h
2
GitHub Stars
36,7 k
Mis à jour
21 nov.
anthropics
Officiel

process-doc

Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.

Installations / 1h
1
GitHub Stars
36,6 k
Mis à jour
20 nov.
anthropics
Officiel

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

Installations / 1h
5
GitHub Stars
36,6 k
Mis à jour
20 nov.
anthropics
Officiel

accessibility-review

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

Installations / 1h
4
GitHub Stars
36,6 k
Mis à jour
20 nov.