capacity-planning plugins

by Claude Code Plugins

Analyze and plan for capacity requirements

by Claude Code Plugins

Analyze and plan for capacity requirements

by Claude Code Plugins

Analyze and plan for capacity requirements

by Filament Labs

Local Codex usage, pace, reset observation, and banked-reset guidance.

by Matt Corbett

Database Reliability Engineering (DBRE) team — agents (dbre-architect, database-operations-engineer, database-incident-responder) that own the PRODUCTION database as a reliability surface, the layer database-engineering (schema/query design) doesn't: HA topology & failover from RPO/RTO, backup & point-in-time recovery with restore verification, disaster recovery, capacity planning, connection pooling; zero-downtime expand-contract migrations, backfills, replication management & failover drills, upgrades; and DB on-call (replication lag, lock contention, connection storms, runaway queries, disk-full), DB SLOs, blameless postmortems. skills, a knowledge bank with Mermaid decision trees + a dated 2026 reference, best-practices, templates. Seams: schema/query → database-engineering; service SRE → observability-sre; provisioning → terraform-iac / cloud; pipelines → data-orchestration; access → security-engineering / auth-identity. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Mortgage Lending Operations specialist team — agents (mortgage-lending-lead, pipeline-pullthrough-analyst, processing-cycle-specialist, compliance-quality-specialist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. An operations team for a production or ops leader accountable for pull-through, cycle time, capacity, and cost-to-originate — it reads pull-through as the funnel and fixes the fallout stage, ties cycle time to capacity and satisfaction, manages lock/pipeline risk, holds cost-to-originate as the unit economic, and routes every compliance question to counsel. Inherits ravenclaude-core protocols.

by Matt Corbett

Performance- and capacity-engineering team — agents (performance-architect, load-testing-engineer, profiling-and-capacity-engineer) for system performance and scalability: performance strategy and budgets, workload modeling, and SLO-linked NFR targets (performance-architect); load/stress/soak/spike testing with k6/Gatling/Locust/JMeter, open- vs closed-model workloads, ramping, think time, and test data (load-testing-engineer); profiling, flame graphs, USE/RED bottleneck triage, capacity and headroom via Little's law, and regression detection (profiling-and-capacity-engineer). Knowledge bank with decision trees, a Little's-law/percentiles capacity calculator, best-practices, skills, commands, templates, an advisory hook, scenarios. Distinct from frontend Core Web Vitals and observability-sre SLOs. Seams: web vitals -> frontend-engineering; SLO -> observability-sre; query tuning -> database-engineering; resilience -> backend-engineering. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Outpatient physical-therapy / rehab clinic operations team — agents (clinic-operations-lead, clinical-documentation-compliance, billing-and-revenue) for the practice-ops + documentation + billing craft of a PT/OT/SLP outpatient clinic: scheduling & capacity and plan-of-care visit cadence, no-show management, defensible POC documentation and medical necessity, certification/recertification timing, the Medicare therapy-threshold + KX concept, CPT timed codes and the 8-minute rule, modifiers (GP/KX/59), and denial prevention. skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands, an advisory hook. ADVISORY only — not medical, legal, or billing advice; every payor/regulatory specific carries a retrieval date + verify-at-use, no patient PII. Seams: medical-revenue-cycle, behavioral-health-practice. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Sales & Revenue Operations specialist team — agents (revops-lead, pipeline-forecast-analyst, funnel-conversion-strategist, quota-territory-architect), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A RevOps team for a sales-ops leader or founder accountable for pipeline, forecast accuracy, and quota attainment — it reads pipeline as coverage-against-quota, forecasts from stage-weighted history, designs quota to capacity, and treats win-rate and sales-cycle as a funnel system. Inherits ravenclaude-core protocols.