Menu

Individual skill

narrative-cascade-planner

0upvotes

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. 叙事落地/逐面消息一致/创意交接简报/画布传导

narrative/land/narrative-cascade-planner/SKILL.md

Read pinned source

Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,135
Repository last updated
Nov 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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/orchestrate/ad-creative-builder/SKILL.md) for ad units, [email-creative-builder](../../../email/engage/email-creative-builder/SKILL.md) for email, [social-creative-builder](../../../social/craft/social-creative-builder/SKILL.md) for social packages, and [message-house-builder](../../../launch/assemble/message-house-builder/SKILL.md) for a launch-window house derived from the canon. It does not author the canon itself ([message-system-architect](../../architect/message-system-architect/SKILL.md) and [narrative-registry](../../../protocol/narrative-registry/SKILL.md) own that — if no canon is on file, route there and stop), build the tier-scoped launch asset manifest ([launch-asset-packager](../../../launch/assemble/launch-asset-packager/SKILL.md)), score cross-surface consistency or compute the TALE profile result ([narrative-quality-auditor](../../evaluate/narrative-quality-auditor/SKILL.md) is the only scorer), or adjudicate claims ([offer-claims-registry](../../../protocol/offer-claims-registry/SKILL.md) is the sole writer of `memory/claims/claims-ledger.md`). It works one lever — landing — and hands off.

## Quick Start

```
Plan the narrative cascade for [product] from our canon. Surfaces: homepage, pricing, store listing, sales deck, social bio, docs, email.
```

```
Write a per-surface message-match spec for our [pricing page / store listing] against the canon and flag any drift.
Back to top