pm-strategy-memolisted

Draft leadership-grade strategy memos using Minto Pyramid (single governing thought → 3-5 supporting arguments → evidence) with a Working Backwards stress-test and a fresh-Claude reader-test before finalizing. Designed for product strategy memos, exec alignment docs, decision memos, positioning memos, and any document that must move a leadership team to a decision. Triggers on "strategy memo", "leadership memo", "exec doc", "alignment doc", "decision memo", "positioning memo", "exec memo", "memo to leadership", "draft a memo", or when the user has a brief, transcript, or thesis and wants to turn it into a memo executives would read. Composes downstream of `interviewer` (context-gather) and `extract-insights` (turn a transcript into a brief) — both from the multiplai-research plugin — and `pm-jtbd-synthesis` / `pm-persona-codifier` (when the memo needs to reference discovery evidence or personas).
spikelab/multiplai-cc-mktplace · ★ 0 · AI & Automation · score 69

Install: claude install-skill spikelab/multiplai-cc-mktplace

# pm-strategy-memo Turn a brief, a thesis, or a pile of context into a memo a leadership team will actually decide on. This is **a decision-forcing artifact**, not an info dump. Every paragraph either moves the reader toward the decision or earns its keep by pre-empting an objection. The skill enforces three things most strategy memos fail at: 1. **Single governing thought.** One sentence at the top that the entire memo defends. Most memos drift across 3-4 competing claims and lose the reader. 2. **Pyramid discipline.** Supporting arguments under the governing thought; evidence under each argument. No floating paragraphs. 3. **Adversarial pre-flight.** The memo passes a Working Backwards stress-test and a fresh-reader test *before* the user sees it. ## Arguments | Arg | Description | Default | |-----|-------------|---------| | **source** | File path (brief, transcript, prior memo), `--from-conversation`, or stated thesis | *(required)* | | `--audience` | Who reads it: `leadership`, `board`, `team`, `cross-functional` | ask | | `--length` | `short` (~600 words / 1 page), `standard` (~1200 words / 2-3 pages), `long` (~2500 words / 4-5 pages) | `standard` | | `--skip-reader-test` | Skip the fresh-Claude reader test (NOT recommended) | `false` | ## Workflow This is a 5-step process. Do not skip the stress-test or reader-test — they're what separate a memo from a draft. ### Step 1 — Context gather (5 questions, asked together) If `--from-conversation`, infer from context.