| name | message-house-builder |
| slug | aaron-message-house-builder |
| displayName | Message House Builder · 消息屋构建 |
| summary | 消息屋/PR-FAQ/价值支柱/发布叙事 |
| description | Use when the user asks to "build a message house", "write a PR-FAQ for our launch", or "define the launch narrative and value pillars"; derives from the positioning canvas a message house — tagline, one-liner, three value pillars, per-persona proof points (each labeled Measured / User-provided / [needs source]) — plus a working-backwards PR-FAQ narrative spine (launch-day tense, empty-chair test, five external + five internal FAQs) and per-channel message angle packs (angles, not finished copy). Not for the positioning canvas itself — use positioning-mapper; not for finished blog posts or pages — use content-writer; not for ad or email units — use each discipline creative builder; not for claim adjudication — use offer-claims-registry. 消息屋/PR-FAQ/价值支柱/发布叙事 |
| 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 launch messaging from a completed positioning canvas: a message house (tagline, one-liner, three value pillars, per-persona proof points), a working-backwards PR-FAQ narrative spine in launch-day tense, and per-channel message angle packs. The messaging layer between positioning (positioning-mapper) and asset production (launch-asset-packager). |
| argument-hint | <product / launch> [personas] [channels] [positioning canvas path] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"assemble","geo-relevance":"low","hermes":{"tags":["marketing","launch","assemble"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Message House Builder
Derives launch-specific messaging from accepted L1 Narrative canon and positioning evidence: a message house, PR-FAQ spine, and per-channel angle packs. It never turns launch copy into a competing brand canon and never adjudicates claims.
Scope guard: this skill turns an existing positioning canvas into messaging only. It does not build the positioning itself (positioning-mapper is the sole upstream — if the canvas is missing, route there first and stop), write finished blog posts or pages (content-writer), produce ad or email units (ad-creative-builder / email-creative-builder), adjudicate claims (offer-claims-registry is the sole writer of memory/claims/claims-ledger.md), or assemble the press kit and asset manifest (launch-asset-packager). It works one lever — messaging — and hands off.
Quick Start
Build a message house for [product] from the positioning canvas. Personas: [list]. Launch channels: [list].
Write a working-backwards PR-FAQ for our [launch type] — launch-day tense, five external + five internal FAQs.
Turn our positioning into per-channel message angles for [Product Hunt / press / store listing / email announcement].
Skill Contract
Expected output: a message house (tagline + one-liner + three value pillars + per-persona proof points, each labeled Measured / User-provided / [needs source]), a PR-FAQ narrative spine (launch-day tense, empty-chair test, numbers over adjectives, five external + five internal FAQs), per-channel message angle packs (angles, not finished copy), a [needs source] claims list for the ledger, and the standard handoff summary.
- Reads: the positioning canvas, personas/channels/tier,
memory/projections/narrative.json, and memory/projections/claims.json at named offsets.
- Writes: the launch house/PR-FAQ/angle packs to with permission; unresolved claims and durable canon changes become separate authorized proposal events.
