capital-allocation

Allocate engineering capacity across initiatives using ROI and hurdle rates.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill capital-allocation-nlightnfotis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capital-allocation
Source: https://github.com/NlightNFotis/skills/tree/main/capital-allocation
Command: npx skills add https://github.com/NlightNFotis/skills --skill capital-allocation-nlightnfotis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams decide where limited engineering capacity should go when too many projects, requests, and obligations compete for the same budget. It turns vague roadmap debates into explicit tradeoff decisions based on return, opportunity cost, hurdle rates, and zero-based re-justification.

Core Features & Use Cases

  • Engineering portfolio allocation: Compare feature work, tech debt, security, infrastructure, research, and support load within one budgeting framework.
  • Kill, defer, or fund decisions: Identify zombie projects, ignore sunk cost, and make clear go/no-go calls based only on future value versus future effort.
  • Run / Grow / Transform balancing: Check whether the team is over-investing in maintenance, expansion, or risky bets and rebalance intentionally.
  • Use case: A platform team must choose between finishing a migration, paying down reliability debt, funding a new product feature, and reserving time for compliance work during quarterly planning.

Quick Start

Ask the capital-allocation skill to rank your current engineering initiatives by ROI, set a hurdle rate, and recommend what to fund, defer, or kill this quarter.

Frequently Asked Questions about capital-allocation

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

FAQPage Schema
How do I prioritize engineering roadmap initiatives by ROI during quarterly planning?

Engineering roadmap prioritization by ROI requires scoring competing demands against expected value and effort, applying hurdle rates and opportunity cost to generate explicit funded, deferred, killed, and not-funded lists for the quarter.

What is zero-based budgeting for engineering portfolio allocation?

Zero-based budgeting for engineering allocation forces teams to re-justify all in-flight projects and new requests from scratch, separating sunk costs from forward decisions to fund only the highest-impact work within a limited capacity budget.

How do I evaluate whether to kill, defer, or fund in-flight projects?

To evaluate killing, deferring, or funding in-flight projects, compare their future value versus future effort while ignoring sunk cost, using established hurdle rates to identify zombie projects and make clear go/no-go calls.

What is the best way to balance Run, Grow, and Transform work in an engineering budget?

Balancing Run, Grow, and Transform work involves comparing maintenance, expansion, and risky bets within one budgeting framework to check for over-investment and intentionally rebalance engineering capacity across competing initiatives.

How do I calculate opportunity cost when choosing between tech debt and new features?

Calculating opportunity cost between tech debt and new features requires scoring both demand types by expected value and cost, revealing the tradeoff of deferred work to ensure limited engineering capacity funds the highest-impact options.

When should I use hurdle rates for headcount allocation decisions?

Hurdle rates should be used for headcount allocation whenever multiple projects compete for the same budget, establishing a minimum ROI threshold to objectively separate funded initiatives from deferred or not-funded work.