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.