Agent skill · Design & Presentation

strategic-narrative-designer

Use when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use mes

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill strategic-narrative-designer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: narrative/architect/strategic-narrative-designer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Strategic Narrative Designer Builds the Raskin-style strategic change narrative — the five-beat arc that reframes a market before any tagline exists: **old world** (the status quo and its now-shaky assumptions) → **the undeniable shift** (what changed that nobody can unsee) → **winners vs losers** (who wins and who is stranded under the new rules) → **the promised land** (the future the shift makes possible) → **proof the promised land is real** (the evidence, each beat labeled and traceable). It is the first move of the TALE **Architect** phase and feeds the `A` dimension's *strategic narrative arc present (old world → the shift → the new game → the promised land → proof), not just a feature list* sub-item (see [tale-benchmark.md](../../../references/tale-benchmark.md)). The arc is the spine [message-system-architect](../message-system-architect/SKILL.md) hangs the durable message house on, so its quality is upstream of the `A1` canon-integrity veto — but this skill authors story structure, never the canon record itself. **Scope guard**: this skill produces the strategic narrative arc *only*. It does **not** author the durable message house — tagline, pillars, boilerplate, canon

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the strategic-narrative-designer skill do?

Use when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use mes

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill strategic-narrative-designer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going