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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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:
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.
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.
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.
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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。