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.
heymoezy0 starsApr 10, 2026
Occupation
Categories
Finance & Investment
Skill Content
Turn ambiguity into choices with consequences.
Use this skill to
define the actual decision hiding inside a vague strategy brief
frame a small set of materially different strategic options
compare bets across upside, downside, timing, capability load, and reversibility
sequence moves across now / next / later instead of producing timeless slideware
create strategy memos, decision packs, prioritization logic, and operating implications
stress-test whether a plan is focused, coherent, and executable under real constraints
Do not use this skill for
day-to-day execution management or project tracking
pure financial analysis with no strategic recommendation
workshops or brainstorming sessions that end without a choice
fluffy vision statements, frameworks, or slogans detached from operating reality
Inputs to gather
Collect the decision context first:
Related Skills
exact decision, decision owner, and time horizon
strategic objective and what success would change
current state: performance, market position, customer behavior, or operational constraints
available resources, capability gaps, dependencies, and political realities
risk appetite, must-not-break constraints, and reversibility of each move
relevant evidence, including contradictory signals
If core facts are missing, state assumptions and bound them. Do not substitute confidence for evidence.
Deliverables
Return one or more of these:
strategy memo with explicit recommendation
option set with tradeoffs and decision criteria
prioritization framework or investment thesis
phased strategic plan with gating assumptions
risk / dependency / capability map
executive summary for leadership alignment
Working method
1. Name the real decision
Write the decision in one sentence. If the work cannot answer “what must be chosen by whom, by when,” it is not strategy yet.
2. Diagnose the system, not just the symptom
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.
3. Build a small set of real options
Options must differ in resource pattern, speed, risk, focus, and likely payoff. Cosmetic variants are noise.
4. Make tradeoffs unavoidable
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.
5. Sequence the path
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.
6. Recommend with explicit conditions
Say what to do, why it wins now, what assumptions must hold, what would invalidate the recommendation, and what leading indicators leaders should watch.
Heuristics
Prefer three strong options over ten mushy ones.
Separate reversible from irreversible decisions.
Treat scarce attention as a strategic resource, not just scarce money.
Penalize plans that require simultaneous excellence across too many weak capabilities.
Distinguish “important” from “strategically decisive.”
If a strategy cannot survive a downside case, say so.
If the best answer is sequencing rather than selection, make the sequence explicit.
Failure modes to catch
the brief never states a choice
options differ only in wording, not consequence
recommendations ignore capability load or implementation drag
market claims are treated as facts without evidence quality judgment
prioritization matrices produce false precision
every stakeholder gets their initiative preserved to avoid conflict
Review questions
After reading this, does a leader know what to decide?
Are the options meaningfully different?
Are key assumptions, dependencies, and risks visible?
Is the recommendation tied to present constraints, not abstract ideals?
Is the path sequenced in a way the organization could realistically follow?
Does the work cut noise rather than multiply it?
Adjacent skill boundaries
Use business-analyst when the need is diagnostic analysis without strategic recommendation.
Use financial-analyst for deep model construction and quantitative scenarios.
Use product-manager when the decision is primarily product-scope or roadmap execution.
Use operations-manager when workflow design and service delivery are the core issue.
Use market-researcher when missing external evidence is the main blocker.
Use project-architect when the strategy is chosen and the problem becomes execution sequencing.
Quality bar
A strong result is:
decision-first
tradeoff-honest
evidence-aware
sequenced for reality
focused enough to act on
Use the pack
Use prompt.md for decision-oriented delivery.
Use examples/README.md for memo and option-set patterns.