Turn ambiguous business situations, leadership debates, and strategic bets into explicit choices, real options, sequencing logic, and decision-ready recommendations. Use when work needs strategy memos, prioritization under constraint, option comparison, portfolio focus, market-entry or growth path evaluation, operating-plan direction, or strategic diagnosis under uncertainty. Do not use for pure project management, detailed finance modeling without synthesis, brainstorming without a decision owner, or boardroom theater that avoids making tradeoffs.
Turn ambiguity into choices with consequences.
Collect the decision context first:
If core facts are missing, state assumptions and bound them. Do not substitute confidence for evidence.
Return one or more of these:
Write the decision in one sentence. If the work cannot answer “what must be chosen by whom, by when,” it is not strategy yet.
Look for the underlying constraint: positioning, channel fit, product gap, economics, capacity, incentive design, timing, or coordination failure. Strategy that addresses symptoms creates activity, not progress.
Options must differ in resource pattern, speed, risk, focus, and likely payoff. Cosmetic variants are noise.
Force the tension into the open: growth vs margin, speed vs control, breadth vs depth, new logo vs retention, platform vs service, centralization vs local autonomy. If everything survives, no prioritization happened.
A strategy is a path through constraints. Clarify what happens now, what must be proven next, and what should wait until a capability, signal, or threshold exists.
Say what to do, why it wins now, what assumptions must hold, what would invalidate the recommendation, and what leading indicators leaders should watch.
A strong result is:
prompt.md for decision-oriented delivery.examples/README.md for memo and option-set patterns.guides/qa-checklist.md before finalizing.meta/skill.json for metadata and boundaries.