设计与多媒体

strategic-narrative-designer

aaron-he-zhu/aa…g-skills

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 message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry. 变革叙事弧/旧世界/应许之地/战略叙事结构

  • 1047 次安装
  • 3000 星标
  • 收录于

安装命令

npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill strategic-narrative-designer

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). The arc is the spine message-system-architect 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 record (that is message-system-architect, which seeds the narrative-registry); build the sales/fundraising pitch deck narrative (pitch-narrative-builder); reconcile positioning against shippable reality (positioning-truth-tracer owns the truth set this reads); adjudicate any product or comparative claim (offer-claims-registry is the sole writer of memory/claims/claims-ledger.md — unverified proof beats are marked [needs source] and submitted to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py); or compute the TALE profile result (only the narrative-quality-auditor gate scores TALE). It works one lever — the arc — and hands off.

Quick Start

Design the change narrative for [product/brand] from the positioning truth set and belief map. Give me the five-beat arc.
Frame the shift our category is going through: old world, the undeniable change, winners vs losers, the promised land, the proof.
Stress-test our current story arc — does the "promised land" beat rest on proof we actually have, or on [needs source] claims?