| name | strat-message-system |
| description | Turns offer, mechanism, MVP, and proof into clear technical messaging: positioning, promise, pillars, hooks, claims, objection matrix, CTA options, FAQ seeds, words to use/avoid, and a skeptical developer explanation. Use after proof-system. |
Message System
Explain the offer to a technical audience with clarity, specificity, and desire.
Workflow
- Load
../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
- Read
.ai/strategy/signal/* and .ai/strategy/offer/*.
- Create positioning, main promise, message pillars, hooks, claim levels, objections, CTA options, FAQ seeds, words to use/avoid, and two explanations: direct version and skeptical-developer version.
- Avoid guru language and broad claims.
- Save
.ai/strategy/gtm/message-system.md.
Output template
# Message System
## Positioning
Format: [Product] is a [category] for [audience] who want [outcome] without [pain/sacrifice].
## Main Promise
## Message Pillars
## Headline Options
## Subheadline Options
## Hook Bank
### Pain Hooks
### Desire Hooks
### Mechanism Hooks
### Proof Hooks
### Speed Hooks
### Risk Reversal Hooks
### Technical Hooks
## Claims
### Safe Claim
### Bold Claim
### Specific Claim
### Technical Claim
## Objection Matrix
| Objection | Hidden Fear | Response | Proof Needed |
|---|---|---|---|
## CTA Options
## FAQ Seeds
## Words To Use
## Words To Avoid
## Non-Marketing Explanation
Explain the offer like speaking to a skeptical developer.
Output quality checklist
- Positioning is specific.
- Claims are aligned with available proof.
- Objection matrix is complete.
- Direct + skeptical explanations are included.
- Words to avoid remove hype and empty claims.
Critical rules
Avoid "revolutionize", "transform your life", "scale effortlessly", "dominate the market", and empty "irresistible offer" language. Prefer clarify, validate, reduce waste, define scope, prove demand, ship, test, and measure.
