deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/message-house
message-house
VerifiedBuild a message house: one roof message, three value pillars, sourced proof, a foundation, and role and channel variants. Use when Marketing, Sales, and partners each tell a different story.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.4 KB |
| examples/sample-industrial.md | markdown | 3.0 KB |
| examples/sample.md | markdown | 3.1 KB |
| template.md | markdown | 1.8 KB |
template.md
View on GitHub# Message House Template
Every unsupported proof point stays `[NEEDS SOURCE]` with the type of proof needed. Quality checks
at the bottom.
---
## 1. Scope
**Offering:** · **Target customer:** · **Positioning statement (link or note absence):**
**Roles in the buying group:** · **Channels:**
## 2. The house
**ROOF (one idea, customer language):**
> [message]
| Pillar | Outcome the customer gets | Traces to (pain or gain, heard where) | Cover test passed? |
|---|---|---|---|
| 1 | | | |
| 2 | | | |
| 3 | | | |
**Proof under each pillar** (strongest first)
| Pillar | Proof point | Type | Source + date, or `[NEEDS SOURCE]` |
|---|---|---|---|
**FOUNDATION (verifiable facts, true today)**
- [years in market, customer or installed-base count, coverage, certifications, attestations]
**Superlatives found:** [quote each] · Basis: · Legal cleared: yes / no
## 3. Variants (same pillars, different emphasis)
| Role | Lead pillar | How it is worded | Proof this role trusts |
|---|---|---|---|
| Channel | Format and length | Why it is good for them | What changes |
|---|---|---|---|
## 4. Words
**Use** (customer's own words, with source): ·
**Avoid** (jargon, unproven superlatives):
## 5. Test plan
**Who (5-8 target customers):** · **What to ask:** what did you hear / believe / doubt?
**Result that changes the house:**
## 6. Committed copy extras
**Proof to Gather (ranked):** 1. · **Messages to Test (ranked):** 1.
---
## Quality checks
- [ ] Roof is one idea, in customer language, consistent with positioning
- [ ] Every pillar is an outcome and passes the cover test
- [ ] Every pillar traces to a pain or gain
- [ ] Every proof point is sourced or flagged; no invented numbers, quotes, or customers
- [ ] Foundation is facts, not adjectives
- [ ] Variants keep the same pillars
- [ ] A test with real customers is planned
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |