existential-birds/beagle / plugins/beagle-analysis/skills/strategy-interview
strategy-interview
VerifiedUse when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.5 KB |
| references/bad-strategy.md | markdown | 6.3 KB |
| references/blue-ocean.md | markdown | 11.7 KB |
| references/kernel.md | markdown | 7.9 KB |
| references/output-template.md | markdown | 8.6 KB |
| references/playing-to-win.md | markdown | 10.4 KB |
| references/pressure-tests.md | markdown | 1.7 KB |
| references/wardley-mapping.md | markdown | 10.8 KB |
references/playing-to-win.md
View on GitHub# The Strategic Choice Cascade
A complementary lens to the kernel. Where the kernel excels at diagnosing a challenge and building a coherent response, the cascade adds structure the kernel underserves: explicitly defining the playing field, the basis of competitive advantage, and the organizational machinery required to execute.
Use this lens in Phase 3 when the strategy involves competitive positioning — choosing where and how to compete. It maps onto and extends the kernel:
- **Winning aspiration** sharpens what the diagnosis is *in service of*.
- **Where to play** and **how to win** together sharpen the guiding policy — they force specificity about the field and the advantage.
- **Capabilities** and **management systems** pressure-test whether the coherent actions are actually feasible.
## When to use this lens vs. the kernel alone
**Use the cascade** when the strategy involves a competitive market: a business choosing segments, a product competing for users, a team positioning itself inside a large org.
**Skip it** when the strategy is purely internal (reorg, process improvement), personal (career pivot), or existential (should we exist at all). The kernel handles these well on its own. Don't force "where to play" onto a problem that has no playing field.
---
## 1. Winning Aspiration
**What it is:** A concrete picture of what winning looks like — not a vision statement, not a revenue target. The state of the world when this strategy has succeeded.
**What makes it good:**
- Specific enough that two people in the org would agree on whether they'd arrived.
- Describes the *impact*, not the effort ("the default tool inspectors reach for" vs. "a market-leading platform").
- Time-bounded or at least stage-bounded.
**What makes it bad:**
- "Be the best." (Best at what? For whom? Measured how?)
- "Maximize shareholder value." (A result, not a picture.)
- Anything that could be pasted into a competitor's deck unchanged.
**Interview prompts:**
- "Forget the mission statement for a second. If this strategy works perfectly, what does the world actually look like in two years? Paint me the picture."
- "Who specifically notices that you've won? What changes for them?"
- "If I visited your company after you'd won, what would I see that's different from today?"
## 2. Where to Play
**What it is:** The choice of playing field — which customers, segments, geographies, channels, categories, or stages of the value chain. This is a *decision*, not a description of where you currently operate.
**What makes it good:**
- Names specific segments *and* names what's excluded.
- Grounded in something the org actually knows about those segments — not aspirational adjacency.
- The chosen field is small enough to dominate, not just participate in.
**What makes it bad:**
- "We serve everyone." (No playing-field choice was made.)
- Segments defined by demographics alone with no behavioral or needs-based logic.
- An attractive market the org has no real reason to win in.
**How it extends the kernel:** "Where to play" forces the guiding policy to be geographically or segment-specific. A guiding policy of "compete on service depth" becomes sharper as "compete on service depth *in the mid-market commercial property segment*." If the user's guiding policy works equally well for every possible customer, it's missing a "where to play" choice.
**Interview prompts:**
- "Who is your ideal customer — not the broadest definition, but the narrowest one where you'd crush it?"
- "What segments are you explicitly *not* going after, and what would change your mind?"
- "If you had to cut your addressable market in half tomorrow, which half do you keep?"
## 3. How to Win
**What it is:** The specific competitive advantage on the chosen playing field. Not "be great" — the mechanism by which you win against the alternatives the customer actually considers.
**What makes it good:**
- Names the advantage *and* why competitors can't easily copy it.
- Rooted in a real asymmetry — cost structure, proprietary data, switching costs, network effects, domain expertise, regulatory position.
- Testable: you could ask a customer "why us over them?" and hear this answer back.
**What makes it bad:**
- "Superior product." (Everyone claims this. What specifically, and why can't they match it?)
- "Better team." (A temporary fact, not a structural advantage.)
- An advantage that requires the competitor to be stupid or asleep.
**How it extends the kernel:** "How to win" is the mechanism inside the guiding policy. The kernel asks for a guiding policy that creates advantage; this forces you to name *what kind* of advantage and *why it holds*. If the user can't articulate the structural reason they win, the guiding policy is aspirational.
**Interview prompts:**
- "If your top competitor hired your best people tomorrow, could they replicate your advantage? If yes, it's not structural."
- "What do you do that's genuinely hard for someone else to copy — not hard to imagine, but hard to *build*?"
- "When a customer picks you over the alternative, what's the real reason? Not the marketing reason — the honest one."
## 4. Capabilities
**What it is:** The 3-5 reinforcing capabilities the organization must have to execute the "where to play" and "how to win" choices. These aren't aspirational — they're the things that must be true about the org.
**What makes it good:**
- Small set (3-5), not a capability wishlist.
- Each capability is specific and observable — you can tell whether the org has it or not.
- The capabilities reinforce each other: having capability A makes capability B stronger.
- At least one capability is hard to build from scratch, creating a barrier.
**What makes it bad:**
- "Innovation." (What kind? Applied where? Measured how?)
- A list of 12 capabilities with no prioritization.
- Capabilities that any well-run company would need — they don't differentiate.
**How it extends the kernel:** Capabilities are the feasibility check on coherent actions. If an action requires a capability the org doesn't have and can't build in the strategy's timeframe, the action is fiction. This is where most strategies quietly break — the actions sound good but assume capabilities that don't exist.
**Interview prompts:**
- "What are the three things your org must be *genuinely good at* for this strategy to work? Not nice-to-haves — load-bearing capabilities."
- "Of those, which ones do you already have, and which ones are you hoping will materialize?"
- "If I talked to someone on your team, would they say the org actually has this capability today — or is it something leadership believes but the front line doesn't experience?"
## 5. Management Systems
**What it is:** The processes, structures, metrics, and feedback loops that keep the strategy on track. The infrastructure of execution — how the org actually operationalizes the choices above.
**What makes it good:**
- Directly tied to the strategy — not generic "good management" practices.
- Includes both measurement systems (how you know it's working) and reinforcement systems (how you prevent drift).
- Addresses the most likely failure modes for *this specific* strategy.
**What makes it bad:**
- "Regular check-ins and dashboards." (Every company says this. What specifically are you measuring, and what changes when the number moves?)
- Systems borrowed from a different strategy that don't fit the current one.
- No system at all — the most common case. The strategy exists in a deck; nothing in the org's operating rhythm references it.
**How it extends the kernel:** The kernel stops at coherent actions. Management systems answer: "And then what? How do you know the actions happened? How do you course-correct?" Most strategies die here — not because the thinking was bad, but because nothing in the organization's daily life changed.
**Interview prompts:**
- "Six months from now, how will you know whether this strategy is working — before the revenue numbers tell you?"
- "What meeting, review, or ritual will force you to look at whether the strategy is on track? If it doesn't exist yet, when will you create it?"
- "What's the most likely way this strategy dies quietly — not with a dramatic failure, but by slow drift back to the old way? What would prevent that?"
---
## Reverse engineering: using the cascade on an existing strategy
When the user brings a strategy that already exists, use the cascade to find gaps. Walk through it top-down:
1. **State the winning aspiration implied by their strategy.** Often it's never been made explicit. Ask: "What does this strategy look like when it's won? Can you describe it concretely?"
2. **Identify the where-to-play choice.** If the strategy applies equally to all customers and segments, flag it: "I notice this doesn't choose a playing field — it reads like it's trying to serve everyone. Is that intentional?"
3. **Name the how-to-win mechanism.** If competitive advantage is implied but not stated, surface it: "What's the structural reason this works for you and not for [obvious competitor]?"
4. **Check capabilities against actions.** For each major action, ask: "Do you currently have the capability to do this, or does the strategy assume you'll build it?" List the assumed capabilities. Most strategies have 2-3 capabilities they assume but haven't resourced.
5. **Look for management systems.** This is almost always the biggest gap. Ask: "What changes in how the org operates day-to-day once this strategy is adopted?" If the answer is "nothing" — flag it clearly in the notes.
The typical pattern: strategies are strongest at the top of the cascade (aspiration, playing field) and weakest at the bottom (capabilities, management systems). The cascade's main diagnostic value is making this gap visible.
---
## Integrating cascade findings into the kernel output
Do not produce a separate cascade document. Instead, fold insights into the kernel:
- **Where to play** findings sharpen the guiding policy's specificity.
- **How to win** findings become the mechanism statement within the guiding policy.
- **Capability gaps** surface as assumptions in `strategy-notes.md` and, if severe, as caveats in the draft: "[DRAFT — assumes capability X exists; needs verification]."
- **Management systems gaps** become items in the "open questions" section of the notes.
In the strategy notes, add a section: "Cascade pressure-test" that captures any findings from the five choices — especially where the strategy was strong vs. where it had gaps.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |