Take a new feature or product update and generate the full

Feature launch playbook

by gooseworks-ai · MIT license · ★ 1,220 on GitHub · updated Sep 21

Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales enablement one-pager. Pure reasoning skill that…

---
name: feature-launch-playbook
description: >
  Take a new feature or product update and generate the full launch kit: changelog entry,
  email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and
  internal sales enablement one-pager. Pure reasoning skill that chains product context
  with audience-specific copy generation. Use when a product marketing team needs to
  turn a feature spec into launch-ready assets fast.
tags: [content]
---

# Feature Launch Playbook

Turn a feature spec or product update into a complete launch kit — every asset you need to announce, from changelog to cold email insert. One input, all outputs.

**Built for:** PMMs or founders who ship features faster than they can write about them. The goal is to go from "feature merged" to "launch assets ready" in one session.

## When to Use

Overview

Turn a feature spec or product update into a complete launch kit — every asset you need to announce, from changelog to cold email insert. One input, all outputs.

What you get

Feature nameWhat are you launching?
One-paragraph descriptionWhat does it do? (Can be a Notion doc, PRD excerpt, or plain text)
Who benefits most?Which ICP segment cares about this? (e.g., "growth teams running outbound")
Problem it solvesWhat was painful before this existed?
Key capabilityThe single most impressive thing it does (for the headline)

Manual install (npx, ZIP)

Claude Codenpx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/gooseworks-ai/goose-skills/tar.gz/615c685f34f8 \
  | tar -xz -C ~/.claude/skills --strip-components=4 goose-skills-615c685f34f8/skills/content/composites/feature-launch-playbook

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/148ecfeafada19944ec5/feature-launch-playbook.zip" -OutFile "$env:TEMP\feature-launch-playbook.zip"; Expand-Archive "$env:TEMP\feature-launch-playbook.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md7.3 KB
skill.meta.json266 B

Read the files here

gooseworks-ai/615c6852 files

SKILL.md

Show the full text286 lines

Feature Launch Playbook

Turn a feature spec or product update into a complete launch kit — every asset you need to announce, from changelog to cold email insert. One input, all outputs.

Built for: PMMs or founders who ship features faster than they can write about them. The goal is to go from "feature merged" to "launch assets ready" in one session.

When to Use

"We just shipped [feature] — help me launch it"
"Write launch copy for [feature/update]"
"I need a changelog entry, email, and LinkedIn post for [feature]"
"Generate the full launch kit for [product update]"
"Turn this feature spec into marketing assets"

Phase 0: Intake

Feature Context

Feature name — What are you launching?
One-paragraph description — What does it do? (Can be a Notion doc, PRD excerpt, or plain text)
Who benefits most? — Which ICP segment cares about this? (e.g., "growth teams running outbound")
Problem it solves — What was painful before this existed?
Key capability — The single most impressive thing it does (for the headline)

Launch Context

Launch tier — How big is this?
- Tier 1 (Major): New product line, major feature, pricing change → Full launch kit
- Tier 2 (Medium): Significant feature, new integration → Email + social + changelog
- Tier 3 (Minor): Small improvement, bug fix → Changelog + social mention
Launch date — When does this go live?
CTA — What should the reader do? (Try it, book a demo, read docs, upgrade)
Visual assets available? — Screenshots, GIFs, demo video URL?

Tone & Voice

Brand voice — Technical/developer, conversational/founder-led, enterprise/professional?
Any messaging to avoid? — Competitor names, specific claims, regulated language?

Phase 1: Core Messaging (Foundation)

Before generating assets, define the messaging foundation:

Feature Positioning Block

HEADLINE: [Outcome-driven, not feature-driven]
  Bad: "Introducing Advanced Filtering"
  Good: "Find your best leads in seconds, not hours"

SUBHEAD: [What it is + who it's for]
  "[Feature name] lets [audience] do [capability] so they can [outcome]."

PROOF POINT: [Metric or before/after comparison]
  "In beta, [customer] saw [X% improvement / saved X hours]."

CTA: [Single clear action]
  "[Try it now / See it in action / Book a demo]"

Phase 2: Generate Launch Assets

Asset 1: Changelog Entry

## [Feature Name] — [Date]

[1-2 sentence summary: what + why it matters]

**What's new:**
- [Capability 1]
- [Capability 2]
- [Capability 3]

**Who it's for:** [ICP segment]

[CTA button text] → [link]

Asset 2: Email Announcement

Subject line options (pick 1, A/B test if possible):
A: [Outcome-driven] — e.g., "Your [workflow] just got 10x faster"
B: [Curiosity-driven] — e.g., "We built the thing you've been asking for"
C: [Direct] — e.g., "New: [Feature Name] is live"

---

Hi [First Name],

[1-sentence hook tied to their pain point]

Today we're launching [Feature Name] — [1-sentence description of what it does].

Here's what this means for you:

- [Benefit 1 — outcome, not feature]
- [Benefit 2]
- [Benefit 3]

[Social proof line if available: "Teams like [Customer] are already using it to [result]."]

[CTA: Try it now / See it in action / Reply to learn more]

[Signature]

P.S. [Urgency or bonus — e.g., "Available on all plans" or "Early access for the next 48 hours"]

Asset 3: LinkedIn Post (Founder Voice)

Generate 3 variants:

Variant A: Story-driven

[Hook: personal story or observation about the problem]

[2-3 lines on why this matters]

Today we shipped [Feature Name].

Here's what it does:
→ [Benefit 1]
→ [Benefit 2]
→ [Benefit 3]

[Social proof or early result]

[CTA — soft: "Check it out" or "Link in comments"]

Variant B: Contrarian/hot take

[Hot take about the problem or industry norm]

[2-3 lines on why the status quo is broken]

So we built [Feature Name] to fix it.

[How it works in 2-3 bullets]

[CTA]

Variant C: Customer-proof-driven

[Customer result or quote as hook]

[Context on what they were doing before]

[Feature Name] made this possible:
→ [Capability that drove the result]

[CTA]

Asset 4: Twitter/X Thread

Tweet 1 (hook):
[Announcement + outcome claim in <200 chars]
🧵

Tweet 2:
The problem: [Pain point in ICP language]

Tweet 3:
What we built: [Feature description + screenshot/GIF]

Tweet 4:
Key capabilities:
- [Bullet 1]
- [Bullet 2]
- [Bullet 3]

Tweet 5:
[Social proof or early result]

Tweet 6:
[CTA + link]

Headline: [6-8 words max]
Body: [1 sentence, 15 words max]
CTA button: [2-3 words]
Dismiss: "Maybe later"

# [Feature Name] — Sales Enablement Brief

## What It Is
[2-3 sentences]

## Who Cares
- [Persona 1]: [Why they care]
- [Persona 2]: [Why they care]

## Talk Track
"[Suggested pitch — 3-4 sentences a rep can use on a call]"

## Objection Handling
| Objection | Response |
|-----------|----------|
| "[Common objection]" | "[Response]" |

## Discovery Questions
- "[Question that surfaces the pain this solves]"
- "[Question that qualifies for this feature]"

## Competitive Context
- [Competitor X]: [Does / doesn't have this]
- [Competitor Y]: [Their approach vs ours]

## Resources
- Demo video: [link]
- Docs: [link]
- Customer story: [link]

Phase 3: Launch Checklist

Generate a launch checklist based on the tier:

Tier 1 (Major Launch)

Changelog entry published
Email announcement sent to [segment]
LinkedIn post published (founder account)
Twitter thread published
In-app banner configured
Sales team briefed (enablement doc sent)
Docs/help center updated
Demo video recorded
Product Hunt post scheduled (if applicable)
Partner/integration notifications sent

Tier 2 (Medium Launch)

Changelog entry published
Email announcement sent
LinkedIn post published
In-app notification configured
Docs updated

Tier 3 (Minor)

Changelog entry published
Social media mention
Docs updated

Phase 4: Output

Save all assets to the current working directory (or user-specified path) under a [feature-slug]/ folder:

launch-kit.md — All assets in one document
checklist.md — Launch checklist with owner assignments

Cost

Component	Cost
All asset generation	Free (LLM reasoning)
Total	Free

Tools Required

None. Pure reasoning skill. Works with any LLM agent.

Trigger Phrases

"Generate launch assets for [feature]"
"We just shipped [feature] — write the launch copy"
"Run the feature launch playbook for [feature]"
"Turn this spec into launch-ready content"

1	---
2	name: feature-launch-playbook
3	description: >
4	Take a new feature or product update and generate the full launch kit: changelog entry,
5	email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and
6	internal sales enablement one-pager. Pure reasoning skill that chains product context
7	with audience-specific copy generation. Use when a product marketing team needs to
8	turn a feature spec into launch-ready assets fast.
9	tags: [content]
10	---
11
12	# Feature Launch Playbook
13
14	Turn a feature spec or product update into a complete launch kit — every asset you need to announce, from changelog to cold email insert. One input, all outputs.
15
16	Built for: PMMs or founders who ship features faster than they can write about them. The goal is to go from "feature merged" to "launch assets ready" in one session.
17
18	## When to Use
19
20	- "We just shipped [feature] — help me launch it"
21	- "Write launch copy for [feature/update]"
22	- "I need a changelog entry, email, and LinkedIn post for [feature]"
23	- "Generate the full launch kit for [product update]"
24	- "Turn this feature spec into marketing assets"
25
26	## Phase 0: Intake
27
28	### Feature Context
29	1. Feature name — What are you launching?
30	2. One-paragraph description — What does it do? (Can be a Notion doc, PRD excerpt, or plain text)
31	3. Who benefits most? — Which ICP segment cares about this? (e.g., "growth teams running outbound")
32	4. Problem it solves — What was painful before this existed?
33	5. Key capability — The single most impressive thing it does (for the headline)
34
35	### Launch Context
36	6. Launch tier — How big is this?
37	- Tier 1 (Major): New product line, major feature, pricing change → Full launch kit
38	- Tier 2 (Medium): Significant feature, new integration → Email + social + changelog
39	- Tier 3 (Minor): Small improvement, bug fix → Changelog + social mention
40	7. Launch date — When does this go live?
41	8. CTA — What should the reader do? (Try it, book a demo, read docs, upgrade)
42	9. Visual assets available? — Screenshots, GIFs, demo video URL?
43
44	### Tone & Voice
45	10. Brand voice — Technical/developer, conversational/founder-led, enterprise/professional?
46	11. Any messaging to avoid? — Competitor names, specific claims, regulated language?
47
48	## Phase 1: Core Messaging (Foundation)
49
50	Before generating assets, define the messaging foundation:
51
52	### Feature Positioning Block
53
54	```
55	HEADLINE: [Outcome-driven, not feature-driven]
56	Bad: "Introducing Advanced Filtering"
57	Good: "Find your best leads in seconds, not hours"
58
59	SUBHEAD: [What it is + who it's for]
60	"[Feature name] lets [audience] do [capability] so they can [outcome]."
61
62	PROOF POINT: [Metric or before/after comparison]
63	"In beta, [customer] saw [X% improvement / saved X hours]."
64
65	CTA: [Single clear action]
66	"[Try it now / See it in action / Book a demo]"
67	```
68
69	## Phase 2: Generate Launch Assets
70
71	### Asset 1: Changelog Entry
72
73	```markdown
74	## [Feature Name] — [Date]
75
76	[1-2 sentence summary: what + why it matters]
77
78	What's new:
79	- [Capability 1]
80	- [Capability 2]
81	- [Capability 3]
82
83	Who it's for: [ICP segment]
84
85	[CTA button text] → [link]
86	```
87
88	### Asset 2: Email Announcement
89
90	```
91	Subject line options (pick 1, A/B test if possible):
92	A: [Outcome-driven] — e.g., "Your [workflow] just got 10x faster"
93	B: [Curiosity-driven] — e.g., "We built the thing you've been asking for"
94	C: [Direct] — e.g., "New: [Feature Name] is live"
95
96	---
97
98	Hi [First Name],
99
100	[1-sentence hook tied to their pain point]
101
102	Today we're launching [Feature Name] — [1-sentence description of what it does].
103
104	Here's what this means for you:
105
106	- [Benefit 1 — outcome, not feature]
107	- [Benefit 2]
108	- [Benefit 3]
109
110	[Social proof line if available: "Teams like [Customer] are already using it to [result]."]
111
112	[CTA: Try it now / See it in action / Reply to learn more]
113
114	[Signature]
115
116	P.S. [Urgency or bonus — e.g., "Available on all plans" or "Early access for the next 48 hours"]
117	```
118
119	### Asset 3: LinkedIn Post (Founder Voice)
120
121	Generate 3 variants:
122
123	Variant A: Story-driven
124	```
125	[Hook: personal story or observation about the problem]
126
127	[2-3 lines on why this matters]
128
129	Today we shipped [Feature Name].
130
131	Here's what it does:
132	→ [Benefit 1]
133	→ [Benefit 2]
134	→ [Benefit 3]
135
136	[Social proof or early result]
137
138	[CTA — soft: "Check it out" or "Link in comments"]
139	```
140
141	Variant B: Contrarian/hot take
142	```
143	[Hot take about the problem or industry norm]
144
145	[2-3 lines on why the status quo is broken]
146
147	So we built [Feature Name] to fix it.
148
149	[How it works in 2-3 bullets]
150
151	[CTA]
152	```
153
154	Variant C: Customer-proof-driven
155	```
156	[Customer result or quote as hook]
157
158	[Context on what they were doing before]
159
160	[Feature Name] made this possible:
161	→ [Capability that drove the result]
162
163	[CTA]
164	```
165
166	### Asset 4: Twitter/X Thread
167
168	```
169	Tweet 1 (hook):
170	[Announcement + outcome claim in <200 chars]
171	🧵
172
173	Tweet 2:
174	The problem: [Pain point in ICP language]
175
176	Tweet 3:
177	What we built: [Feature description + screenshot/GIF]
178
179	Tweet 4:
180	Key capabilities:
181	- [Bullet 1]
182	- [Bullet 2]
183	- [Bullet 3]
184
185	Tweet 5:
186	[Social proof or early result]
187
188	Tweet 6:
189	[CTA + link]
190	```
191
192	### Asset 5: In-App Banner / Notification
193
194	```
195	Headline: [6-8 words max]
196	Body: [1 sentence, 15 words max]
197	CTA button: [2-3 words]
198	Dismiss: "Maybe later"
199	```
200
201	### Asset 6: Internal Sales Enablement One-Pager (Tier 1 only)
202
203	```markdown
204	# [Feature Name] — Sales Enablement Brief
205
206	## What It Is
207	[2-3 sentences]
208
209	## Who Cares
210	- [Persona 1]: [Why they care]
211	- [Persona 2]: [Why they care]
212
213	## Talk Track
214	"[Suggested pitch — 3-4 sentences a rep can use on a call]"
215
216	## Objection Handling
217	\| Objection \| Response \|
218	\|-----------\|----------\|
219	\| "[Common objection]" \| "[Response]" \|
220
221	## Discovery Questions
222	- "[Question that surfaces the pain this solves]"
223	- "[Question that qualifies for this feature]"
224
225	## Competitive Context
226	- [Competitor X]: [Does / doesn't have this]
227	- [Competitor Y]: [Their approach vs ours]
228
229	## Resources
230	- Demo video: [link]
231	- Docs: [link]
232	- Customer story: [link]
233	```
234
235	## Phase 3: Launch Checklist
236
237	Generate a launch checklist based on the tier:
238
239	### Tier 1 (Major Launch)
240	- [ ] Changelog entry published
241	- [ ] Email announcement sent to [segment]
242	- [ ] LinkedIn post published (founder account)
243	- [ ] Twitter thread published
244	- [ ] In-app banner configured
245	- [ ] Sales team briefed (enablement doc sent)
246	- [ ] Docs/help center updated
247	- [ ] Demo video recorded
248	- [ ] Product Hunt post scheduled (if applicable)
249	- [ ] Partner/integration notifications sent
250
251	### Tier 2 (Medium Launch)
252	- [ ] Changelog entry published
253	- [ ] Email announcement sent
254	- [ ] LinkedIn post published
255	- [ ] In-app notification configured
256	- [ ] Docs updated
257
258	### Tier 3 (Minor)
259	- [ ] Changelog entry published
260	- [ ] Social media mention
261	- [ ] Docs updated
262
263	## Phase 4: Output
264
265	Save all assets to the current working directory (or user-specified path) under a `[feature-slug]/` folder:
266	- `launch-kit.md` — All assets in one document
267	- `checklist.md` — Launch checklist with owner assignments
268
269	## Cost
270
271	\| Component \| Cost \|
272	\|-----------\|------\|
273	\| All asset generation \| Free (LLM reasoning) \|
274	\| Total \| Free \|
275
276	## Tools Required
277
278	None. Pure reasoning skill. Works with any LLM agent.
279
280	## Trigger Phrases
281
282	- "Generate launch assets for [feature]"
283	- "We just shipped [feature] — write the launch copy"
284	- "Run the feature launch playbook for [feature]"
285	- "Turn this spec into launch-ready content"
286