anthropics/knowledge-work-plugins

capacity-plan

Plan resource capacity — workload analysis and utilization forecasting.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill capacity-plan

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

/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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

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

1時間の導入数
2
GitHub Stars
3.7万
更新日
11月21日
anthropics
公式

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.

1時間の導入数
1
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

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.

1時間の導入数
5
GitHub Stars
3.7万
更新日
11月20日
anthropics
公式

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.

1時間の導入数
4
GitHub Stars
3.7万
更新日
11月20日