existential-birds/beagle / plugins/beagle-analysis/skills/strategy-review
strategy-review
VerifiedUse 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.0 KB |
| references/interview-lens-audit.md | markdown | 10.1 KB |
| references/judge-artifact-schema.md | markdown | 29.8 KB |
| references/pressure-tests.md | markdown | 8.9 KB |
| references/review-dimensions.md | markdown | 21.8 KB |
| references/review-lenses.md | markdown | 17.4 KB |
| references/review-template.md | markdown | 9.0 KB |
references/pressure-tests.md
View on GitHub# Pressure-test scenarios
Expected behaviors for the strategy-review skill. Use these to validate that the skill handles common review entry points correctly.
| Scenario | Expected behavior |
|----------|-------------------|
| User provides a standalone goals document (all aspirations, no diagnosis) | Name it: "This reads more like a goals document than a strategy." Rate Diagnosis as Missing, Bad-Strategy Patterns as Weak (goals masquerading as strategy). Offer to help identify the missing strategic elements. |
| User provides `strategy-draft.md` only, notes exist but weren't offered | Ask for `strategy-notes.md` — the notes dramatically enrich the review. Proceed without if user declines. |
| Draft + notes mismatch: notes contain sharper thinking than draft | Flag in Notes Cross-Reference: "The interview produced a sharper diagnosis than the draft contains." Quote both versions. |
| Polished board deck with weak diagnosis | Calibrate to near-final maturity — higher bar, flag everything that undermines credibility. Focus on the diagnosis gap specifically because a polished presentation with a vague diagnosis is the most dangerous kind of bad strategy. |
| Comparative review: two competing proposals | Review each independently first using the seven dimensions, then compare. Don't declare a winner unless structural quality clearly differs. |
| Mid-interview provisional draft (`[PROVISIONAL]` tag) | Produce a "mid-interview check" with 3-5 observations, not a full review. Focus on strongest and weakest emerging kernel elements. Suggest questions to pressure-test before finalizing. |
| Strategy with sourced market claims | Check which claims are sourced vs. asserted. Flag conventional wisdom presented as fact. Note claims you can't verify: "I can't verify this, but if wrong, the strategy changes." If durable state is active, tag claims in `source-evidence.md`. |
| Long multi-appendix document (>3,000 words) | Activate durable review state. Extract evidence to `source-evidence.md` during reading. Compose final review from artifacts, not conversation memory. |
| User says "poke holes in this" or "quick take" | Deliver findings inline in chat — lead with Critical Findings, top failure path, recommendations. Offer to write full `strategy-review.md` afterward. Do not write the file without confirming. |
| Strategy already in execution (post-hoc review) | Focus on assumption validation — which assumptions can now be checked against reality? Flag any already falsified by events. |
| Strategy uses OKRs/V2MOM/SWOT instead of kernel language | Evaluate the thinking, not the format. Map concepts to kernel. Flag genuine structural gaps ("this V2MOM has methods but no diagnosis") rather than forcing vocabulary. |
| Notes contain Wardley findings (evolution stages, value-chain dependencies, inertia insight); draft drops them | Flag in interview lens audit: "Landscape mapping — Partially reflected" or "Missing." Identify the specific findings that were dropped — e.g., notes say "our data pipeline is custom-built but three vendors now offer this as a product" but the draft says "we face competitive pressure in infrastructure." Quote both versions. Record under Dim 1 (diagnosis quality) because the landscape insight was meant to sharpen the diagnosis. Do NOT substitute Five Forces questions to validate the Wardley findings — Five Forces tests competitive pressure, not value-chain mapping fidelity. |
| Notes contain cascade capability gaps; draft treats them as action items | Flag in interview lens audit: "Strategic choice cascade — Partially reflected." The cascade identified a capability the org doesn't have as a *risk*; the draft treats it as a *task* ("hire mobile team by Q3"). Record under Dim 6 (assumption exposure) — the gap between "we need this capability" and "we have this capability" is a load-bearing assumption. |
## Judge artifact mode scenarios
| Scenario | Expected behavior |
|----------|-------------------|
| Normal review — user says "review this strategy" with no judge/JSON language | Produce only `strategy-review.md` (or chat-only feedback). Do NOT emit `strategy-review.json`. No mention of JSON artifacts unless the user asks. |
| User says "produce a machine-readable review" or "LLM judge output" | Activate judge artifact mode. Produce `strategy-review.md` first, then `strategy-review.json`. JSON must parse as valid JSON, contain all seven dimension ratings and all five bad-strategy pattern entries, and every score must match its label per the mapping (Strong=4, Adequate=3, Weak=2, Missing=1). |
| User says "JSON only" or "just the evaluation artifact" | Produce only `strategy-review.json`, skip the prose file. All validation rules still apply. |
| Judge mode review of a strategy with missing diagnosis | JSON `dimension_ratings[0]` (diagnosis_quality) must have `score: 1, label: "Missing"`. The `critical_findings` array must include a finding about the missing diagnosis. That finding's title must appear in `blocking_findings`. The `reward_signal.pass` must be `false` because blocking findings are non-empty. The rationale must cite the missing diagnosis. |
| Judge mode review where interview notes contain Wardley lens findings that were dropped from the draft | JSON `interview_lens_audit` must include an entry with `lens: "landscape_mapping"` and `assessment: "partially_reflected"` or `"missing"`. The `dropped` array must name the specific findings lost between notes and draft. The `evidence` array must contain at least one `notes_cross_ref` entry (the original finding) and one `doc_quote` entry (what replaced it or the absence). The prose review's Lens Findings section must contain the same audit finding. |
| Judge mode — weighted total and reward signal arithmetic | `aggregate_score.weighted_total` must equal `Σ(score × weight / 100)` within ±0.01. `reward_signal.score` must equal `(weighted_total - 1.0) / 3.0` within ±0.01. `reward_signal.pass` must be `true` only when `weighted_total ≥ 2.5` AND `blocking_findings` is empty. |
| Judge mode — prose and JSON consistency | Every dimension label in JSON must match the rating in `strategy-review.md`. Every critical finding title in JSON must appear in the prose Critical Findings section. If the prose says "Diagnosis Quality — Weak" but the JSON has `score: 3, label: "Adequate"`, that is a validation failure. |
| Judge mode — adequate aggregate with blocking findings | Strategy scores Adequate or above on aggregate (`weighted_total ≥ 2.5`) but has a critical finding in `blocking_findings`. The `reward_signal.pass` must be `false` despite the adequate aggregate. The `rationale` must cite the blocking finding, not the score. This validates that blocking findings gate independently of the aggregate — the AND condition in the pass/fail logic requires BOTH adequate score AND empty blocking findings. |
| Judge mode — happy path (all dimensions Strong) | Strategy is structurally sound on every dimension. All seven `dimension_ratings` have `score: 4, label: "Strong"`. Every dimension's `recommendation` is `null`. No `bad_strategy_patterns` entries are detected (`detected: false` for all five). `blocking_findings` is empty. `aggregate_score.weighted_total` is 4.0 with `label: "Strong"`. `reward_signal.pass` is `true` and `reward_signal.score` is 1.0. `critical_findings` still has 2–4 entries — even a strong strategy has soft spots — but each is severity `moderate` at most and none appear in `blocking_findings`. If `strengths` is emitted, it has 2–4 entries. The prose Review Summary must not bury or invent flaws to balance the assessment; if the strategy is genuinely strong, say so. |
| Judge mode — durable review state active with judge artifact mode | User invoked judge artifact mode on a long multi-appendix document for which durable review state was activated (per the "Long multi-appendix document" scenario in the table above). The skill must produce `strategy-review.md` and `strategy-review.json` in the user's working directory AND also write `strategy-review.json` to the durable review state directory. Both copies must be byte-identical. If `strategy-notes.md` was present, the JSON must include the `notes_cross_reference` object. If interview lenses appear in the notes, the JSON must include `interview_lens_audit` with `evidence` entries that include at least one `notes_cross_ref` provenance tag pointing into the durable state files. The `review_metadata.review_id` should be emitted so pipeline consumers can deduplicate the dual-written artifact. Validation: read both copies and confirm the dual-write happened and that they match. |
| Judge mode — partial-write failure during dual-write | One of the two write locations succeeds while the other fails (disk full, permission denied, path not found). The skill must warn about the failed write location but still complete the review — the successful copy is usable. The warning must name which location failed and include the error. Do not retry or roll back the successful write. |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |