Use when the user asks to "optimize resources", "level resources", "run what-if scenarios", "resolve over-allocations", "balance resource demand", or mentions resource leveling, resource smoothing, optimization, what-if analysis, resource allocation optimization, capacity balancing.
TL;DR: Performs resource optimization through leveling and smoothing techniques, resolving over-allocations while minimizing schedule impact. Runs what-if scenarios to evaluate the impact of resource changes (additions, removals, reallocation) on schedule, cost, and quality.
Resource leveling intercambia tiempo por recursos; resource smoothing intercambia eficiencia por estabilidad. La elección depende de qué es más escaso: si el deadline es inflexible, suavizar; si los recursos son inflexibles, nivelar. What-if scenarios convierten "qué pasaría si" de especulación en análisis cuantificado.
resource-plan# Full resource optimization with leveling
/pm:resource-optimization $ARGUMENTS="--schedule schedule.md --resources resource-plan.md"
# What-if scenario comparison
/pm:resource-optimization --type what-if --scenarios "add-dev,delay-phase2,reduce-scope"
# Smoothing only (preserve deadline)
/pm:resource-optimization --type smoothing --deadline 2026-09-30
Parameters:
| Parameter | Required | Description |
|---|---|---|
$ARGUMENTS | Yes | Path to schedule and resource plan |
--type | No | full (default), leveling, smoothing, what-if |
--scenarios | No | Comma-separated what-if scenario names |
--deadline | No | Hard deadline for smoothing constraint |
--threshold | No | Max allocation % (default 80%) |
{TIPO_PROYECTO}: All project types benefit from optimization. Waterfall uses traditional leveling algorithms; Agile uses velocity-based capacity adjustment; SAFe uses PI-level load balancing; Portfolio uses cross-project resource optimization.
**/resource_calendar* to verify availability data is current [SCHEDULE]Good example — Quantified optimization:
| Attribute | Value |
|---|---|
| Over-allocations found | 4 resources at 110-130% |
| Leveling result | 3 resolved within float, 1 requires schedule extension |
| What-if scenarios | 3 scenarios compared with schedule/cost/quality impact |
| Recommendation | Scenario B selected — add 1 FTE for 3 sprints |
| Before/after | Resource histograms showing peak reduction from 130% to 85% |
| Schedule impact | +3 days on non-critical path, critical path preserved |
Bad example — Manual redistribution: "Move some tasks around so nobody is overloaded." No dependency analysis, no float calculation, no impact quantification. Manual redistribution without respecting dependency logic creates impossible schedules.
| Resource | When to read | Location |
|---|---|---|
| Body of Knowledge | Before starting to understand standards and frameworks | references/body-of-knowledge.md |
| State of the Art | When benchmarking against industry trends | references/state-of-the-art.md |
| Knowledge Graph | To understand skill dependencies and data flow | references/knowledge-graph.mmd |
| Use Case Prompts | For specific scenarios and prompt templates | prompts/use-case-prompts.md |
| Metaprompts | To enhance output quality and reduce bias | prompts/metaprompts.md |
| Sample Output | Reference for deliverable format and structure | examples/sample-output.md |
Resolves resource bottlenecks. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Rebalances capacity across teams. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Enforces sustainable pace. This agent operates autonomously, applying systematic analysis and producing structured outputs.
Analyzes utilization patterns. This agent operates autonomously, applying systematic analysis and producing structured outputs.