본문으로 건너뛰기
cccskills
무료GitHub에 공개

portfolio-strategy

Compare business lines, products, and markets by attractiveness and your ability to win. Rank investment options by the value of the next dollar, and document funding, harvesting, or exit decisions with evidence and reversal signals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Decides 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.

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Allocating budget across business lines
  • Reviewing whether a product deserves more investment
  • Ranking competing initiatives
  • Planning a responsible business exit

포함된 파일(2)

  • SKILL.md3.6 KB
  • references/sources.md1.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Portfolio strategy

Most organizations fund by inertia. Last year's allocation plus a percentage, adjusted by who argued hardest. Portfolio strategy is the discipline of deciding again, deliberately.

Assess each line on two axes

Attractiveness — is this a good place to be? Market size and growth, structural profitability, concentration of buyer power, regulatory direction, and how the economics behave as it scales.

Right to win — is it good for us? Our position relative to alternatives, the assets or capabilities that transfer, and whether the advantage is durable or borrowed.

The combination gives you four postures, and the honest one is usually uncomfortable:

  • Attractive, we can win — fund properly. Underfunding these is the most common and most expensive portfolio error.
  • Attractive, we cannot win — the seductive trap. Everyone wants in on a good market. Entering without an advantage funds someone else's growth.
  • Unattractive, we can win — harvest. Run for cash, do not invest for growth.
  • Neither — exit. Slowly and reluctantly is how these consume a decade of attention.

Judge on marginal return, not absolute size

The question is never "is this business good." It is "what does the next dollar do here versus elsewhere." A large profitable line may be a poor place for incremental investment; a small one may be the best.

Watch for cross-subsidy. A weak line supported by a strong one is a decision, and it should be an explicit one with a thesis and an end date — not an accident nobody has looked at.

Exit is the hardest decision and the most valuable

Sunk cost, internal advocates, and the discomfort of admitting a bet failed all argue for one more year. The test is prospective: knowing what we know now, would we start this today? If not, the only question is how to exit well.

Exiting frees more than the money. It frees the attention of the people running it, which is usually the scarcer resource.

Plan exits properly: customer commitments, employee treatment, and contractual obligations. A badly run exit costs more than the business was losing.

Running a review

Same evidence for every line, prepared by a neutral party rather than by each line's advocate. Set the criteria and weights before seeing the numbers — weighting afterward reproduces the allocation you already had.

Force a ranking. Tiers are how everything stays funded.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Fund a line because it is large. Fund it on marginal return.
  • Keep a line alive on sunk cost.
  • Starve a line without deciding to exit it. Slow starvation costs more than a clean exit.
  • Review the portfolio only when a line is already in trouble.

Return contract

Each line with its posture and evidence, the recommended allocation and what changed from last period, what you are stopping, and the indicator that would reverse each call.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design and review access so people and services have appropriate permissions. Use it to plan roles, audit accounts, reduce always-on admin rights, manage credentials, handle departures, and improve sign-in with single sign-on or multi-factor authentication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing who can access each system
  • Planning role based permissions
  • Removing access during offboarding
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Plan account-based marketing for a defined set of companies. Assess whether the economics fit, prioritize accounts, map the people involved in buying, coordinate outreach across sales and marketing, and track account movement through the pipeline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assess whether account-based marketing fits the business
  • Build and prioritize a target account list
  • Map buying roles within target companies
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Improve the path from signup to a new user’s first meaningful result. Define the action that signals real value, refine signup and onboarding, and diagnose where people drop off so more accounts become active users sooner.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing or fixing signup and onboarding
  • Finding why signups do not become active users
  • Reducing time to a first meaningful result
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Design a repository’s multi-agent structure by assigning exclusive file areas, defining builder and reviewer roles, and checking ownership rules with a CI script. Use it to divide work, prevent overlapping edits, and decide whether another agent is needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Dividing repository work among agents
  • Defining agent roles and file ownership
  • Auditing overlapping agent responsibilities
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Use this skill to define an AI system’s intended use, evaluate its errors across user groups, plan monitoring and meaningful human review, and document its limits. It supports deployment and retirement decisions, especially when AI could affect consequential outcomes for people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Set evaluation criteria before deployment
  • Investigate model behavior drift
  • Plan monitoring and human review
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Use this skill to analyze markets, map competitors, assess trends, and compare strategic options such as market entry or build versus buy. It produces a cited research brief that separates established facts from inferences and estimates, states confidence, and connects findings to a decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Sizing a market or analyzing an industry
  • Mapping competitors and buyer differences
  • Comparing market entry or build versus buy
cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고