crew-scaling

Evaluates metrics to decide when to add, remove, or parallelize agent roles.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-scaling-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-scaling
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/plugin/crew/skills/crew-scaling
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-scaling-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running multi-agent workflows often add agents or parallelize prematurely, wasting context tokens and creating race conditions without improving throughput. This Skill forces an evidence-based review of review quality, bottleneck location, and work independence before any scaling change is recommended. ## Core Features & Use Cases - Three-question diagnostic: Checks defect detection rates from .crew/metrics.md, identifies where work actually waits, and verifies whether work units can genuinely run in parallel. - Tiered role ladder: Maps roles (explorer, security, developer, dba, planner, and more) to tiers 0-3 with explicit trigger conditions for each addition, kept in sync with crew_state.ROLE_TIERS via a committed test. - Cost accounting: States the per-role context cost on every invocation so growth decisions are weighed against measurable value in metrics. - Use Case: A user asks to "add three more developer agents" to speed up a single repo. The Skill checks the metrics, finds the bottleneck is human review attention, and recommends against the change instead of blindly scaling. ## Quick Start Ask the agent to review whether the current crew setup should grow, shrink, or parallelize based on recent metrics.

Frequently Asked Questions about crew-scaling

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

FAQPage Schema
How do I decide when to add more agents to a multi-agent workflow?

Check three things first: whether review is catching 0.3-2.0 defects per ticket, where work actually waits, and whether the work units are independent. Only add a role when a recurring defect class justifies it, naming the role after that failure mode.

When does parallelizing agents across repos actually increase throughput?

Parallelism works on independent work units such as separate repos or git worktrees of one repo. Two agents sharing one working tree create conflicting edits and lost writes, which costs more than the time saved.

Why is adding more agents a bad idea when review is the bottleneck?

If work is waiting on human review attention, more agents produce more parallel output for the same reviewer, worsening the queue. The correct fix is addressing review capacity, not agent count.

How do I remove an agent role from the crew configuration?

Run /crew:pm offboard <role> instead of hand-editing config.json. The offboard path requires naming the coverage the removal loses, which a direct edit would skip.

What does each additional agent role cost in a Claude Code crew?

Each role costs a full context load plus the entire CLAUDE.md hierarchy on every invocation. Six roles at 3k tokens of standing context means 18k tokens paid repeatedly, which must show measurable value in metrics.md.