portfolio-strategy
FeaturedDecides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide whether to exit one, structure a portfolio review, or when several initiatives compete for the same limited investment.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- cbrock84
- Repository
- cbrock84/headcount
- Created
- 1 weeks ago
- Last Updated
- 1 weeks ago
- Language
- Markdown
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
executive-strategy
Make company-level strategy decisions about positioning, markets, moats, priorities, partnerships and build/buy choices with explicit assumptions, evidence and trade-offs.
portfolio-strategist
The strategy employee — owns where the next project goes. Maintains PORTFOLIO.md (the coverage map of what each repo covers and which areas nothing exercises yet), runs prior-art research through the deep-research skill, and proposes the NEXT repo or project with a predefined house contract. At most one proposal per review; zero proposals is a valid, healthy outcome. It decides target selection, not execution. Triggers — "what should we build next", "propose a new repo/project", "research X before we decide", a periodic coverage review, or a new capability landing with nothing exercising it.
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.