capacity

Analyze 30-day agent and council metrics to identify capacity pressure and bottlenecks.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill capacity-brucebanner010198-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capacity
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/capacity
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill capacity-brucebanner010198-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Capacity signals tell the COO and roster-manager where pressure exists across the agency, enabling proactive planning and risk mitigation.

Core Features & Use Cases

  • Per-agent utilization and bands across 30 days to surface idle, low, healthy, hot, and overloaded resources.
  • Council-level bottleneck detection and parallel-dispatch analysis to identify throughput risks.
  • Integrated output in census.md and roster workflows to inform staffing, project sequencing, and KR coverage decisions.
  • Use Case: during roster checkpoint, see who is overloaded and restructure assignments before kickoff.

Quick Start

Request a real-time capacity snapshot across all agents and councils for the current planning cycle.

Frequently Asked Questions about capacity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify agent capacity bottlenecks and overloaded resources across my organization?

To gauge capacity pressure, it reads 30 days of roster data, dispatch logs, and KR coverage signals to compute utilization bands classifying agents as idle, healthy, hot, or overloaded. This surfaces actionable signals for proactive roster management.

How do I calculate per-agent utilization bands for roster management?

Per-agent utilization bands are calculated by reading 30 days of roster data and dispatch logs to classify resources as idle, low, healthy, hot, or overloaded. This informs staffing and project sequencing decisions during roster checkpoints.

What is council-level bottleneck detection and how does parallel-dispatch analysis work?

Council-level bottleneck detection uses parallel-dispatch analysis to identify throughput risks across the organization. It applies per-council metrics to 30 days of dispatch logs to surface actionable signals for roster management.

Can I use capacity signals for proactive planning during a roster checkpoint?

Yes, you can request a real-time capacity snapshot across all agents and councils for the current planning cycle. This snapshot reveals overloaded resources and bottlenecks, enabling you to restructure assignments before kickoff.

What data sources do I need to compute utilization bands and surface capacity pressure?

Computing utilization bands requires reading roster data, dispatch logs, and KR coverage signals across a 30-day window. These integrated inputs surface capacity pressure and inform staffing, project sequencing, and KR coverage decisions.