strategic-narrative-generator
$
npx mdskill add mohitagw15856/pm-claude-skills/strategic-narrative-generatorTurn 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.
SKILL.md
.github/skills/strategic-narrative-generatorView on GitHub ↗
--- name: strategic-narrative-generator description: "Generate the strategic story connecting a product roadmap to company goals in a form non-technical stakeholders can repeat. Use when asked to explain the roadmap, present strategy to leadership or the board, write the why behind the roadmap, create a narrative for all-hands, or make the roadmap tell a story. Produces a themed narrative with executive summary, progression arc, hard-question preparation, and what's-not-on-the-roadmap section." --- # 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
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.