narrative-cascade-planner
Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline''s creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same s
npx skills add aaron-he-zhu/aaron-marketing-skills --skill narrative-cascade-planner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Narrative Cascade Planner Maps the narrative-registry canon onto every owned surface as a per-surface message-match spec and cuts a handoff brief to each discipline's creative builder. It is the first move of the TALE **Land** phase and feeds the `L` dimension of [tale-benchmark.md](../../../references/tale-benchmark.md) — the *cascade plan exists*, *per-channel angle packs derived from the canon not improvised*, *objection reframes consistent across surfaces*, and *proof placed where the claim is made* sub-items. It is the upstream of the `TALE L1` message-match veto: if a flagship surface contradicts the canon's tagline, pillars, or approved claim wording, the cascade plan is where that drift is caught before the surface ships, not after the gate blocks it. The plan is a routing-and-spec artifact — it never writes the surface copy and never adjudicates a claim. **Scope guard**: this skill produces the cascade plan and per-surface message-match specs only. It does **not** write the finished surface copy — that goes to each discipline's creative builder: [content-writer](../../../seo-geo/implement/content-writer/SKILL.md) for pages and long-form, [ad-creative-builder](../../../ad
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the narrative-cascade-planner skill do?
Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline''s creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same s
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill narrative-cascade-planner --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.