Windsurf + Aider targets, MCP server, and demo placement (#33)

Broadens both reach (more tools) and content types (an MCP server), continuing
the multi-platform story.

Windsurf + Aider:
- build-exports.mjs gains two platforms: exports/windsurf/*.md (workspace rules,
  trigger: model_decision) and exports/aider/*.md (conventions for `aider --read`).
  Now 5 platforms (ChatGPT, Gemini, Cursor, Windsurf, Aider).
- install.sh + bin/cli.mjs install both (windsurf -> .windsurf/rules, aider ->
  .aider/skills with a --read hint); generated README index is excluded from copies.
- One-line windsurf-install.sh / aider-install.sh wrappers for parity.

MCP server (new content type):
- mcp/server.mjs — zero-dependency stdio MCP server exposing list_skills,
  search_skills, get_skill. Published as a second bin (pm-claude-skills-mcp).
  Logs to stderr; reads bundled skills/ at startup. mcp/README.md documents
  client config.

Also: README hero "See it in action" demo placement (ready to swap in a GIF;
recording guide in web/docs-assets/README.md), Works-With table + exports +
install docs updated, CHANGELOG Unreleased. package.json files/bin updated.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>

exports/aider/pm-strategy/strategic-narrative-generator/strategic-narrative-generator.md

@@ -0,0 +1,72 @@
+# Strategic Narrative Generator Skill
+
+Turn a prioritised initiative list into a strategic narrative — the story that explains not just what you're building but why, why now, and why this sequence.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Prioritised initiative list** (with rough timelines)
+- **Current OKRs or strategic priorities** (1-3)
+- **Audience** (board, leadership team, all-hands, investors)
+- **Competitive or market context** (optional but improves output significantly)
+
+## Process
+1. Identify 2-3 natural strategic themes from the initiative list
+2. For each theme: articulate the problem, the customer it serves, and the metric it moves
+3. Build the progression narrative: how does Q1 set up Q2? How does H1 set up H2?
+4. Write executive summary in under 100 words (the version someone can repeat)
+5. Anticipate the 3 hardest questions a sceptical board member would ask — draft answers
+6. Identify what's NOT on the roadmap and why
+7. **Validate** — Confirm every initiative maps to a theme. If an initiative is orphaned, either create a theme for it or flag it as a narrative gap.
+
+## Output Structure
+
+### Product Strategy Narrative: [Period]
+
+**The One-Paragraph Context:**
+[Market moment + key challenge + our response — for the CFO, not the engineer]
+
+**Strategic Theme 1: [Name]**
+- The problem: [customer pain in plain language]
+- Our response: [initiatives in this theme]
+- The metric it moves: [specific and measurable]
+- Why now: [timing rationale]
+
+**Strategic Theme 2: [Name]**
+[Same structure]
+
+**The Progression Story:**
+[How each quarter sets up the next — this is the narrative arc]
+
+**Executive Summary (under 100 words — shareable):**
+[Version someone can quote at a board meeting]
+
+**Questions to Prepare For:**
+1. [Hard question] → [Prepared answer]
+2. [Hard question] → [Prepared answer]
+3. [Hard question] → [Prepared answer]
+
+**What's Not on the Roadmap (and Why):**
+[2-3 items — shows strategic discipline, not just prioritisation]
+
+## Tone
+- Write for a CFO, not an engineer
+- Lead with outcomes, not features
+- Every sentence should answer "so what?"
+- Avoid jargon — if you can't say it plainly, the strategy isn't clear enough yet
+
+## Quality Checks
+
+- [ ] Executive summary is under 100 words and can stand alone
+- [ ] Every initiative in the input maps to a strategic theme
+- [ ] Each theme has a specific, measurable metric (not "improve engagement")
+- [ ] Progression story shows causal links between quarters, not just chronological listing
+- [ ] "Not on the roadmap" section includes at least 2 items with clear rationale
+
+## Anti-Patterns
+
+- [ ] Do not produce a narrative that lists initiatives chronologically without showing causal progression — the story must show why each phase enables the next
+- [ ] Do not use abstract strategic language that cannot be repeated by a non-technical listener — test whether someone could explain it back without the document
+- [ ] Do not omit the "what's not on the roadmap" section — what you are choosing not to do is as important as what you are doing
+- [ ] Do not set themes without measurable metrics — a theme without a metric cannot be tracked or held to account
+- [ ] Do not skip the hard questions section — preparing for objections in advance is the purpose of the narrative exercise