| name | narrative-cascade-planner |
| slug | aaron-narrative-cascade-planner |
| displayName | Narrative Cascade Planner · 叙事落地规划 |
| summary | 画布落地/逐面消息一致/创意交接简报 |
| description | 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 story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when the narrative-registry canon is on file and the message must now propagate to every owned surface: mapping per-surface message-match specs (which claim, pillar, proof, and objection reframe each of homepage / pricing / store listing / sales deck / social bio / docs / email carries) and cutting a handoff brief to each discipline's creative builder. The first Land-phase move after the canon is sealed, and the upstream of the TALE L1 message-match veto. Not the finished copy itself and not consistency scoring. |
| argument-hint | <product / brand> [surfaces to cover] [target creative builders] [canon path] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"narrative","phase":"land","geo-relevance":"low","hermes":{"tags":["marketing","narrative","land"],"category":"narrative"},"openclaw":{"emoji":"📖","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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 — 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 for pages and long-form, ad-creative-builder for ad units, email-creative-builder for email, social-creative-builder for social packages, and message-house-builder for a launch-window house derived from the canon. It does not author the canon itself (message-system-architect and narrative-registry own that — if no canon is on file, route there and stop), build the tier-scoped launch asset manifest (launch-asset-packager), score cross-surface consistency or compute the TALE profile result (narrative-quality-auditor is the only scorer), or adjudicate claims (offer-claims-registry is the sole writer of ). It works one lever — landing — and hands off.
