pitch-narrative-builder

name	pitch-narrative-builder
slug	aaron-pitch-narrative-builder
displayName	Pitch Narrative Builder · 路演叙事构建
summary	融资/销售路演叙事：问题→拐点→产品英雄→证据→要点
description	Use when the user asks to "build our pitch deck narrative", "write a fundraising story", or "structure the sales pitch narrative"; derives from the narrative canon a company pitch/deck narrative — problem → the undeniable shift → product-as-hero → proof → the ask — as a slide-beat outline (one narrative beat per slide, with the claim ID each proof beat rests on), for both a sales pitch and a fundraising deck. Every proof beat is labeled Measured / User-provided / '[needs source]' and unverified ones route to the claims candidates. Not for the launch-window battle cards and talk track — use sales-enablement-kit; not for the durable message hierarchy or the arc itself — use message-system-architect / strategic-narrative-designer; not for finished deck visual design — out of scope; not for claim adjudication — use offer-claims-registry. 路演叙事/融资故事/销售 pitch/幻灯节拍
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 deriving a company pitch narrative from an existing narrative canon: the problem → shift → product-as-hero → proof → ask arc rendered as a per-slide beat outline for a sales pitch or a fundraising deck, with each proof beat tied to a claim-ledger ID. The Land-phase expression of the canon in deck form — distinct from launch-window sales-enablement-kit and from the durable arc (strategic-narrative-designer). Not the battle cards, not the message hierarchy, not the finished slide design.
argument-hint	<company / product> [audience: investors|sales|both] [canon path] [story bank 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"}}

Pitch Narrative Builder

Derives the company pitch/deck narrative from the narrative canon — the problem → the undeniable shift → product-as-hero → proof → the ask arc, rendered as a slide-beat outline (one narrative beat per slide) for both a sales pitch and a fundraising deck. It sits in the Land phase of the TALE loop and expresses the canon in deck form: it feeds L (the sales deck is a flagship surface that must match the canon's tagline, pillars, and claim wording — the message-match sub-item) and A (the deck is the arc's most public expression) — see tale-benchmark.md. It is derived from, and must not fork, the durable canon: the pitch is a restatement, never a second source of truth.

Scope guard: this skill produces the pitch narrative and its slide-beat outline only. It does not write launch-window battle cards or a rep talk track (reuse sales-enablement-kit — that is a launch asset, this is the durable company narrative in deck form), author the durable message hierarchy (message-system-architect) or the strategic arc itself (strategic-narrative-designer — if no canon exists, route there first and stop), design finished slides (visual design is out of scope), build the reusable story units it draws on (story-bank-builder), or adjudicate claims — every unverified proof is marked [needs source] and submitted to memory/events/claims.ndjson via an authorized operation: propose request to registry-events.py for offer-claims-registry, and this skill never adjudicates substantiation. It works one lever — the deck narrative — and hands off.

Quick Start

Build our pitch deck narrative for [company] from the canon. Audience: investors. Story bank: [path or "help me pull from canon"].

Structure a sales pitch narrative for [product] — problem → shift → product-as-hero → proof → the ask — one beat per slide.

Turn our narrative canon into an investor deck outline and flag every proof slide that has no ledger-approved claim behind it.