From skills-for-humanity
Guides analysis of resource allocation decisions by making trade-offs explicit across competing claims, constraints, and strategic priorities.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-resource-allocation-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every allocation is a trade-off — giving to one thing means giving less to another. The problem is that most allocations are made implicitly, leaving the trade-offs invisible. Making trade-offs explicit forces honest prioritisation and prevents the political habit of pretending everything can be fully funded.
Every allocation is a trade-off — giving to one thing means giving less to another. The problem is that most allocations are made implicitly, leaving the trade-offs invisible. Making trade-offs explicit forces honest prioritisation and prevents the political habit of pretending everything can be fully funded.
Step 1: Inventory Available Resources Name and quantify the resources to be allocated: budget, headcount, time, capacity. Be precise about what is actually available — not what is desired.
Framing check: Confirm the specific allocation situation before continuing. State what resources you've identified and the decision context they apply to in one sentence, then use AskUserQuestion:
Step 2: List All Competing Claims Every demand on the resource. Include maintenance and ongoing commitments, not just new initiatives. Claims that are implicitly assumed to be funded should be made explicit here.
Step 3: Assess Each Claim For each claim: what is the strategic priority (how directly does this serve the most important goals)? What is the cost of under-resourcing it (what breaks, slows, or is lost if it receives less)?
Step 4: Identify Constraints Are there minimums (must have at least X to function), maximums (more than Y produces no additional value), or dependencies (A must be funded before B makes sense)?
Step 5: Draft an Allocation Distribute the available resource across claims. At this stage, make the trade-offs explicit: write down what each claim gives up under this draft allocation.
Step 6: Sense-Check Against Overall Goals Does this allocation, taken as a whole, serve the most important outcomes? Where is the allocation driven by politics or inertia rather than strategic priority?
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
| Resource | Total Available |
|---|---|
| ... | ... |
| Claim | Strategic Priority | Cost of Under-Resourcing | Constraints |
|---|---|---|---|
| ... | High / Medium / Low | ... | Min / Max / Dependency |
| Claim | Allocation | Trade-off (what it gives up) |
|---|---|---|
| ... | ... | ... |
Does this allocation serve the most important outcomes? Where does it diverge from strategic priority — and is that divergence justified?
The most useful output is the trade-off column — if the trade-offs can't be written clearly, the allocation hasn't been thought through. Force each trade-off to be named before the allocation is finalised.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-resource-bottleneck-analysis — Find bottlenecks in the current allocation/s4h-decision-criteria-weighting — Weight criteria by resource constraints/s4h-resource-waste-audit — Audit for waste in the current allocationnpx claudepluginhub human-avatar/skills-for-humanityRoutes resource allocation, bottleneck, leverage, and waste analysis. Use to diagnose capacity constraints or decide where to focus effort.
Allocates engineering resources across products by assessing team size, ROI, urgency, and risk, then generating a prioritization matrix and allocation plan.
Applies opportunity cost analysis to resource allocation decisions by evaluating next-best alternatives and the cost of inaction. Useful for feature prioritization, build-vs-buy, architecture choices, and time/money commitments.