Skip to content

Kartik-Doye/Ravengard-AI-Recruiter / agent/skills/headroom

headroom

Verified

Plans capacity, performance, and resilience from measured or explicitly estimated demand. Use for scalability decisions, growth planning, service targets, bottleneck forecasts, queue or cache sizing, and Now/Next/Scale plans. Do not use to debug a known slow path or implement a feature.

FileKindSize
SKILL.mdskill md13.6 KB
references/dimensions.mdmarkdown2.0 KB
references/research.mdmarkdown4.5 KB

references/dimensions.md

View on GitHub
# Capacity dimensions

Read only the dimensions that can change the current decision.

## Workload

Record observed values where available and label estimates:

- traffic rate and peak-to-average shape;
- concurrency and burst duration;
- read and write mix;
- request fan-out and payload size;
- data volume, growth, retention, and index overhead;
- latency and availability objectives;
- recovery point and recovery time objectives;
- budget and operational staffing.

Show arithmetic with units. A sample estimate is not a capacity fact.

## Bottlenecks

For each likely bottleneck, record:

- resource or dependency;
- evidence of current utilization;
- failure behavior as saturation approaches;
- the metric that would trigger action;
- the cheapest change that creates headroom;
- new cost, consistency, and operational failure modes.

Consider compute, memory, storage, database locks, connections, queues, network,
third-party quotas, hot keys, and human on-call capacity.

## Architecture choices

Use the failure that must be prevented to choose among:

- vertical scaling, horizontal scaling, and workload isolation;
- caching and invalidation;
- batching, queues, and backpressure;
- replication, partitioning, and sharding;
- stronger or weaker consistency;
- single-region and multi-region deployment;
- modular monolith and separately deployed services.

Do not add a mechanism merely because a growth scenario can be imagined.

## Now, Next, Scale

| Horizon | Content |
| --- | --- |
| Now | simplest design that meets current measured needs |
| Next | one low-regret preparation plus a measurable trigger |
| Scale | larger change, evidence that would justify it, migration path, and cost |

A scenario multiplier may be useful for sensitivity analysis, but it must be
labeled as a scenario chosen for the current task, not a universal forecast.

## Failure and recovery

If reliable workload data is missing, return the smallest safe design and the
measurement needed next. If a recommendation depends on an untested assumption,
state the counterfactual that would reverse it.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall