Skip to content

existential-birds/beagle / plugins/beagle-analysis/skills/strategy-interview

strategy-interview

Verified

Use 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).

FileKindSize
SKILL.mdskill md30.5 KB
references/bad-strategy.mdmarkdown6.3 KB
references/blue-ocean.mdmarkdown11.7 KB
references/kernel.mdmarkdown7.9 KB
references/output-template.mdmarkdown8.6 KB
references/playing-to-win.mdmarkdown10.4 KB
references/pressure-tests.mdmarkdown1.7 KB
references/wardley-mapping.mdmarkdown10.8 KB

references/pressure-tests.md

View on GitHub
# Pressure-test scenarios

Expected behaviors for the strategy-interview skill. Use these to validate that the skill handles common entry points correctly.

| Scenario | Expected behavior |
|----------|-------------------|
| User says "write a strategy to grow 30%" | Enter discovery, do not produce a draft — "grow 30%" is a goal, not a strategy |
| User provides an existing strategy doc | Start with bad-strategy filter before discovery |
| User stops mid-interview (short interview, no `.beagle` state) | Write `strategy-notes.md` with resume state only, no `strategy-draft.md` |
| User describes a feature arms race | Deploy value innovation prompts from blue-ocean lens |
| User asks for career strategy | Skip Wardley/cascade unless conversation warrants them |
| User says "just critique this, don't rewrite it" | Use critique variant, respect chat-only if requested |
| Long interview with 15+ substantive exchanges | Create/update `.beagle/strategy/<subject-slug>/state.md`; compose final documents from artifacts, not raw transcript |
| Conflicting stakeholder views surface | Capture both sides in `evidence.md` with `contested` tags; surface the disagreement in notes rather than averaging it away |
| User stops mid-interview (`.beagle` state exists) | Update `.beagle/strategy/<subject-slug>/state.md` with resume state; optionally produce `strategy-notes.md`; no `strategy-draft.md` |
| Phase 4 after long interview | Write `composition.md` first; compose `strategy-draft.md` and `strategy-notes.md` from `.beagle` artifacts, not chat memory |
| Multiple possible strategy subjects emerge | Scope to one, park the rest in `state.md` open questions or `evidence.md` decisions |
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall