Skip to main content
ClaudeWave
ES, Spanish
Skill1.5k estrellas del repoactualizado 5d ago

capital-allocation

Allocate a finite budget or headcount across competing initiatives by return and strategic fit. Use when asked to allocate budget, decide where to invest, build a funding/portfolio plan, or make trade-offs across initiatives under a cap. Produces a capital-allocation plan — initiatives scored by expected return × strategic fit per dollar, a funded/unfunded split against the cap, the cut line, and the reasoning.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/capital-allocation && cp -r /tmp/capital-allocation/plugins/pm-business/skills/capital-allocation ~/.claude/skills/capital-allocation
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Capital Allocation Skill

Allocating capital is the core executive job: a fixed pot, more good ideas than money, and the need to
say no on the record. This skill scores initiatives by expected return *and* strategic fit per unit of
cost, allocates against the cap (honouring must-funds), and makes the **cut line** explicit — so funding
is a defensible portfolio choice, not the loudest voice in the room.

## Required Inputs

Ask for these only if they aren't already provided:

- **The cap** — the total budget or headcount to allocate, and the period.
- **The initiatives** — each with its cost, expected return (revenue, savings, or a strategic value), and strategic fit.
- **Constraints** — anything that *must* be funded (compliance, keep-the-lights-on) or can't be partially funded.
- **The objective** — what you're optimising: near-term return, strategic positioning, or a balance.

## Output Format

### Capital Allocation: [pot], [period]

**1. Objective & cap** — what you're optimising and the total available.

**2. Scored initiatives** — a table; score = expected value × strategic fit, normalised per unit cost:

| Initiative | Cost | Expected return | Strategic fit (1–5) | Score / $ | Must-fund? |
|---|---|---|---|---|---|

**3. The allocation** — funded vs. unfunded against the cap, with budget utilisation. Must-funds first, then highest score/$ until the cap binds.

**4. The cut line** — the marginal initiative that *just* missed, and what it would take to fund it (the most useful number for the debate).

**5. Rationale & trade-offs** — why the portfolio is balanced this way, what's deliberately not funded, and the reversibility of each bet.

**6. Re-evaluation triggers** — what would change the allocation mid-period (a bet pays off early, a must-fund grows).

## Programmatic Helper

`scripts/capital_allocate.py` (stdlib only) does the allocation deterministically — must-funds first, then
by score-per-cost until the cap binds — and reports the cut line:

```bash
# items.json: [{"name":"Mobile revamp","cost":300,"expected_return":900,"strategic_fit":5,"must_fund":false}, ...]
python3 scripts/capital_allocate.py items.json --budget 1000
python3 scripts/capital_allocate.py items.json --budget 1000 --json
```

## Quality Checks

- [ ] Initiatives are scored on expected return AND strategic fit, not return alone
- [ ] Score is expressed per unit of cost, so cheap-good beats expensive-good fairly
- [ ] Must-funds are honoured before discretionary allocation
- [ ] The cut line is explicit — the marginal initiative and what it'd take to fund it
- [ ] What's deliberately not funded is stated, with the trade-off

## Anti-Patterns

- [ ] Do not allocate by last year's split or by who argues hardest — score the portfolio
- [ ] Do not rank by absolute return — a $900 return on $300 beats $1000 on $900; use return per dollar
- [ ] Do not ignore strategic fit — the highest-ROI initiative can still be off-strategy
- [ ] Do not hide the cut line — the initiatives that just missed are the real decision, and the team deserves to see it
- [ ] Do not treat estimates as facts — expected returns are usually [hunch]/[external]; flag the confidence

## Based On

Portfolio capital-allocation practice — expected-value × strategic-fit scoring per unit cost, against a hard constraint.
360-feedback-templateSkill

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

401k-plan-decoderSkill

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

ab-test-plannerSkill

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

ab-test-readoutSkill

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

accessibility-auditSkill

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

accessible-travel-plannerSkill

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

accommodation-requestSkill

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.

account-planSkill

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.