GTM Templates

This skill provides templates for go-to-market communications.

Templates

Template	Purpose
`templates/blog-post.md`	Launch blog post
`templates/changelog.md`	Changelog entry
`templates/enablement.md`	Internal enablement

Blog Post Structure

Hook (1 paragraph)

Why should the reader care? What problem does this solve?

Context (1-2 paragraphs)

What's the background? Why now?

What Shipped (2-3 paragraphs)

What's the feature? What can you do with it?

How It Works (2-3 paragraphs)

Technical details with code examples.

Getting Started (1 paragraph + code)

First steps to try it.

What's Next (1 paragraph)

Future direction (without commitments).

Changelog Format

Use Keep a Changelog format:

markdown

## [1.2.0] - 2024-01-15

### Added
- New feature description

### Changed
- Modified behavior description

### Deprecated
- Feature being phased out

### Removed
- Deleted feature

### Fixed
- Bug fix description

### Security
- Security fix description

Social Media

•Professional tone
•150-300 words
•Industry context
•Call to action

Twitter/X

•Concise (<280 chars)
•Punchy language
•Thread for depth
•Visual if possible

Email Announcement

code

Subject: [Feature Name] is now available

[One sentence: what shipped]

[1-2 sentences: why it matters]

[Call to action button]

[Optional: quick start link]

Enablement Brief

Talking Points (3-5 bullets)

Key messages for customer conversations.

Competitive Positioning

How this compares to alternatives.

Objection Handling

Common objections and responses.

Demo Script

Step-by-step demo instructions.

FAQ

Technical and commercial questions.

Voice Guidelines

•Technical and precise: Use specific terms
•Confident not arrogant: Show, don't claim
•Kubernetes-native: Use ecosystem terminology
•Multi-tenancy aware: Platform for providers
•Open source friendly: Credit the ecosystem

gtm-templates