# Messaging framework Human Guide

## What This Is For
When to Use Creating new sales plays, launch content, or talk tracks. It gives the agent a clearer input/output frame for messaging framework: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Messaging framework agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for messaging framework.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Messaging framework guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Creating new sales plays, launch content, or talk tracks.
- Refreshing messaging for competitive shifts or product updates.
- Enabling partners or success teams with consistent narratives.
- **Audience & Pain** – define persona, current pains, and desired state.
- **Value Pillars** – articulate 2-3 core benefits with supporting proof.
- **Proof & Stories** – attach metrics, customer quotes, ROI snippets, demos.
- **Objection Handling** – map common objections to concise responses.
- **CTA & Next Step** – specify recommended actions (demo, workshop, business case).
- Message house worksheet (persona, pain, value, proof, CTA).
- Story library index referencing assets.
- Tailor variations per segment/industry but keep pillars consistent.
- Partner with product marketing for latest proof points.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the Messaging framework human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `messaging-framework`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Enablement Messaging Framework Skill

## When to Use
- Creating new sales plays, launch content, or talk tracks.
- Refreshing messaging for competitive shifts or product updates.
- Enabling partners or success teams with consistent narratives.

## Framework
1. **Audience & Pain** – define persona, current pains, and desired state.
2. **Value Pillars** – articulate 2-3 core benefits with supporting proof.
3. **Proof & Stories** – attach metrics, customer quotes, ROI snippets, demos.
4. **Objection Handling** – map common objections to concise responses.
5. **CTA & Next Step** – specify recommended actions (demo, workshop, business case).

## Templates
- Message house worksheet (persona, pain, value, proof, CTA).
- Objection/response matrix.
- Story library index referencing assets.

## Tips
- Tailor variations per segment/industry but keep pillars consistent.
- Partner with product marketing for latest proof points.
- Revisit after every major launch or pricing change.

---