strategy-review

Solid

Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).

Code & Development 61 stars 8 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Strategy Review Pressure-test strategy documents to find where they'll break before reality does it for you. The primary job isn't to evaluate prose quality or check formatting — it's to find the gaps, hidden failure paths, and under-accounted risks that will kill the strategy in execution. A strategy that survives this review has a meaningfully better chance of surviving contact with the real world. This skill complements the `beagle-analysis:strategy-interview` skill. Strategy-interview helps *build* a strategy through guided conversation; strategy-review subjects an existing strategy to rigorous adversarial evaluation using the same kernel framework (diagnosis, guiding policy, coherent actions) and bad-strategy filter. ## What makes this different from generic feedback Most strategy feedback falls into two useless categories: vague praise ("this is really thoughtful") or surface-level nitpicking ("consider adding a timeline"). Neither helps the author see whether their thinking actually holds up under stress. This review does three things that generic feedback doesn't: 1. **Tests structural integrity** — whether the logical chain from diagnosis through guiding policy to coherent actions actually holds together, or whether the "therefore" between them is secretly an "and also." 2. **Hunts for failure paths** — not just what's wrong with the document, but what goes wrong in the *real world* because of what's missing. The slow drift scenario, the capability gap that s...

Details

Author
existential-birds
Repository
existential-birds/beagle
Created
5 months ago
Last Updated
today
Language
Shell
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

strategy-interview

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

61 Updated today
existential-birds
AI & Automation Listed

good-strategy

Strategy evaluation and design framework based on Richard Rumelt's "Good Strategy Bad Strategy" and Michael Porter's "What Is Strategy?". Use this skill whenever the user is discussing strategy, plans, priorities, vision, roadmaps, OKRs, or competitive positioning — even if they do not explicitly say "good strategy", "Rumelt", "Porter", or "strategy kernel". Triggers include: (1) evaluating whether a strategy is good or bad, (2) diagnosing the core challenge before proposing solutions, (3) building a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-testing strategic plans with pre-mortem analysis, (5) distinguishing strategy from goals, ambitions, or wish lists, (6) diagnosing strategy claims that are actually just goals, visions, or budgets dressed up as strategy, (7) reviewing a "strategy doc", "strategic priorities", "strategic plan", or "strategic objectives" for fluff and incoherence, (8) evaluating Porter's five forces, value chain, or competitive positioning conversa

0 Updated 3 days ago
tomaszstaniak
AI & Automation Listed

strategic-review

Deep multi-phase strategic review of a specific decision — premise challenge, alternatives, risk map, adversarial review. Use for big choices (wedge, pricing, channel, hire, pivot). For quick framework lookup, use decision-playbook. For diagnosing why something is broken, use business-investigation.

0 Updated today
Layneformalized225
Code & Development Solid

iterative-plan-review

Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan — including terse commands like "iterate", "refine it", or "iterate for correctness" where a plan is present in context. Also use it when the user asks to verify, validate, or confirm feasibility of an approach (e.g., "can you verify this will work", "check this for correctness", "is this sound") — the defining signal is that the user wants critical evaluation of a proposed approach, not execution of it. Produces two companion files in an artifacts/ subfolder next to the plan: review-findings.md (every finding raised and how it was resolved) and review-iteration-history.md (round-by-round record of specialists engaged and plan changes applied). Do NOT use for implementing plan steps, generating new plans from scratch, writing te

69 Updated 2 days ago
testdouble
Code & Development Listed

ia-document-review

Structural review of documents for gaps, clarity, completeness, and organization. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.

20 Updated today
iliaal