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/bad-strategy.md
View on GitHub# Bad Strategy: Patterns to Catch in Real Time
There are four hallmarks of bad strategy (Rumelt's canonical set), plus one additional anti-pattern. Listen for all five constantly during the interview and redirect when you hear them. The user will often not realize they're doing it — these patterns feel like strategy from the inside.
## 1. Fluff
**What it sounds like:** Abstract, buzzword-heavy language that creates an illusion of expertise without conveying actual content.
**Classic tells:**
- "Synergies," "leverage," "ecosystem," "platform play," "holistic approach"
- "Customer-centric," "data-driven," "world-class"
- "Transformational," "next-generation," "best-in-class"
- Any sentence that could appear unchanged in any other company's deck
**Why it's dangerous:** Fluff lets people feel like they've said something meaningful without committing to any claim that could be wrong. It's strategy-shaped language.
**Redirection scripts:**
- "Can you translate that into something concrete? What would a skeptic see on a Tuesday that tells them this is happening?"
- "If I recorded a video of someone doing this well, what would I see them doing?"
- "Pretend I'm a new engineer on the team — describe it in plain words."
## 2. Failure to Face the Challenge
**What it sounds like:** The conversation is about ambitions, targets, and aspirations, but nobody has said what the actual obstacle is. When you ask "what's the problem?" you get a description of the desired outcome instead.
**Classic tells:**
- "We want to be the leader in X." (What's stopping that?)
- "We need a strategy for growth." (Growth is prevented by what?)
- "Our strategy is to win in Europe." (Why aren't you winning already?)
- Long SWOT analyses with no prioritization, no narrative, no "therefore."
**Why it's dangerous:** If you don't name the obstacle, you can't tell whether any action would help. You end up doing everything, which is the same as doing nothing.
**Redirection scripts:**
- "What's stopping this from already being true?"
- "If this is so obviously good, why haven't you done it yet? What's in the way?"
- "Let's work backwards. What's the *problem* that this outcome would solve?"
- "What would have to be true for us to succeed — and which of those things is currently not true?"
## 3. Mistaking Goals for Strategy
**What it sounds like:** "Our strategy is to grow revenue 30% YoY while improving margins and expanding internationally." That's a goal stack with zero information about *how* or *why that how*.
**Classic tells:**
- Any "strategy" statement that is entirely numbers and outcomes
- OKRs presented as strategy
- "We will become the #1 player in..."
- Mission statements with targets bolted on
**Why it's dangerous:** Goals tell you where you want to end up. Strategy is the theory of how getting there is actually possible given real obstacles and finite resources. Without that theory, you're just wishing louder.
**Redirection scripts:**
- "Okay — that's the goal. What's the theory of how it happens?"
- "What has to be true about the world, or about us, for this to work?"
- "If you woke up tomorrow and this had happened, what would be the story of how? Who did what?"
- "A competitor has the same goal. What are we doing differently that makes us more likely to hit it?"
## 4. Bad Strategic Objectives
Two sub-flavors:
### 4a. The "dog's dinner" — a laundry list
**What it sounds like:** 11 priorities, each with 4 sub-priorities, all marked "high importance." Nothing has been traded off.
**Why it's dangerous:** A list without priority is not strategy; it's an inventory of wishes. When resources are scarce (always), everything-is-important means nothing-is-important.
**Redirection scripts:**
- "If you could only do three of these, which three?"
- "Which of these, if done well, makes the others easier?"
- "What's on this list because it's actually important, and what's on it because someone would be upset if it weren't?"
### 4b. Blue-sky objectives
**What it sounds like:** The "strategy" restates the problem as if naming it solved it. ("We will eliminate technical debt." "We will become a product-led organization.")
**Why it's dangerous:** It assumes away the work. If eliminating tech debt were easy, it would already be eliminated. The strategy needs to explain what changes about *how*, not just declare that it will happen.
**Redirection scripts:**
- "What's the mechanism? What changes that makes this possible now when it wasn't before?"
- "If this were easy, it would already be done. What's the thing that has to give?"
## 5. Strategy by Analogy (additional anti-pattern)
**What it sounds like:** References to what successful companies did, presented as self-evident justification. "Spotify did squads, so we should too." "Netflix has a culture deck, let's write one."
**Classic tells:**
- "X did it and it worked"
- Company names used as strategy arguments
- Copying visible practices without understanding invisible prerequisites
- "We should do what [company] does" without examining fit
**Why it's dangerous:** The success conditions of the original strategy are invisible. The adopter copies the *what* without the *why*, and the structural context that made it work. Spotify's squads worked because of Spotify's engineering culture, hiring bar, and product shape — not because someone drew a matrix on a whiteboard.
**Redirection scripts:**
- "That worked for [company] under specific conditions — what's similar about your situation, and what's different? Which of those differences could break the approach?"
- "What problem were they solving when they did that? Is that the same problem you have?"
- "What's the part of their approach you *can't* see from the outside? That's usually where the magic is."
## Posture when pushing back
Push back directly but stay on the user's side. You are not a critic; you are a careful reader of their thinking. Frame pushback as curiosity ("help me understand...") rather than judgment.
If the user pushes back on your pushback, don't escalate — note the disagreement in `strategy-notes.md` as an open question and keep moving. The goal is a better document at the end, not winning an argument in the middle.
If the user explicitly says they don't want to be challenged on a particular point right now, respect that and flag it in the notes file. Sometimes people need to think out loud before they're ready to stress-test.
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 |