launch-announcement

Name: launch-announcement
Author: Productfculty-aipm

70stars33forks

How to install launch-announcement?

productfculty-aipm/pm-copilot-by-product-faculty/launch-announcement

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill launch-announcement

Installs into the current project.

Summary

Use this skill when the user asks to "write a launch announcement", "announce this feature", "write a launch email", "product announcement", "release notes", "launch blog post", "feature announcement to customers", "write the Slack announcement for this launch", or is preparing t

Files · 1

View on GitHub

SKILL.md

1	# Launch Announcement
2
3	You are writing launch communications — the external-facing message that converts a shipped feature into user awareness, adoption, and delight. Every launch announcement is a marketing and retention opportunity.
4
5	Frameworks: April Dunford (positioning clarity), Lenny's PRD guide (problem-oriented framing), copywriting principles (benefits over features).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for: product name, stage, primary persona, current roadmap (to understand what just shipped), and stakeholder communication preferences. Read `context/product/personas.md` for tone calibration.
10
11	## Step 2 — Frame the Announcement Around the Problem
12
13	The #1 launch communication mistake: announcing a feature instead of announcing a solution.
14
15	- ❌ "We've added dark mode" → This is a feature
16	- ✓ "You asked for an easier way to use [Product] at night. Dark mode is here." → This is a solution
17
18	Every announcement should:
19	1. Reference the user problem or request
20	2. Show the solution in concrete terms (what can they do now that they couldn't before?)
21	3. End with a clear next action
22
23	## Step 3 — Determine the Format
24
25	Different channels need different formats:
26
27	In-app notification: 1–2 sentences. CTA button. No context needed.
28	Email announcement: Subject line + 3–4 short paragraphs. Problem → Solution → How to access → CTA.
29	Slack/Discord message: Conversational tone. Brief. Include a visual or GIF if possible.
30	Blog post / changelog: Full narrative. 300–600 words. Problem, solution, how it works, what's next.
31	LinkedIn post: Conversational, first-person. Story-forward. Include a real example or quote.
32	Product Hunt post: Tagline + body. Includes what problem it solves, who it's for, and how to try it.
33
34	Ask which format(s) the user needs.
35
36	## Step 4 — Write the Announcement
37
38	For each format requested, write:
39
40	Subject/headline: The benefit, not the feature name. "Now you can [do X] without [pain Y]"
41
42	Opening: Acknowledge the user's struggle or the request. Show you've been listening.
43
44	What's new: Describe the feature in user terms. What does the user do? What happens? What outcome do they get?
45
46	Why it matters: One sentence connecting the feature to user impact.
47
48	How to access: Clear, specific instructions. Don't assume they'll find it.
49
50	What's next: Optional. If there's more coming in this area, hint at it — creates anticipation.
51
52	CTA: One clear action: "Try it now", "See it in action", "Give us feedback".
53
54	## Step 5 — Tone Calibration
55
56	Calibrate tone based on:
57	- Product stage (from memory): Early-stage = scrappy and warm. Growth-stage = confident and product-led. Scale = polished and authoritative.
58	- Primary persona (from memory): Technical users want precision. Non-technical users want reassurance. Enterprise stakeholders want reliability signals.
59	- Channel: Blog = editorial. Email = personal. Slack = casual. LinkedIn = professional-but-human.
60
61	## Step 6 — Output
62
63	Produce:
64	- Launch announcement in all requested formats
65	- A "don't forget" checklist: in-app tooltip? Help doc? Customer success heads-up? Support team briefed?
66	- Suggested send time if relevant

People who liked this also viewed

6 picks

Type

launch-announcement

70stars33forks

View on GitHub

How to install launch-announcement?

productfculty-aipm/pm-copilot-by-product-faculty/launch-announcement

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill launch-announcement

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Launch Announcement
2
3	You are writing launch communications — the external-facing message that converts a shipped feature into user awareness, adoption, and delight. Every launch announcement is a marketing and retention opportunity.
4
5	Frameworks: April Dunford (positioning clarity), Lenny's PRD guide (problem-oriented framing), copywriting principles (benefits over features).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` for: product name, stage, primary persona, current roadmap (to understand what just shipped), and stakeholder communication preferences. Read `context/product/personas.md` for tone calibration.
10
11	## Step 2 — Frame the Announcement Around the Problem
12
13	The #1 launch communication mistake: announcing a feature instead of announcing a solution.
14
15	- ❌ "We've added dark mode" → This is a feature
16	- ✓ "You asked for an easier way to use [Product] at night. Dark mode is here." → This is a solution
17
18	Every announcement should:
19	1. Reference the user problem or request
20	2. Show the solution in concrete terms (what can they do now that they couldn't before?)
21	3. End with a clear next action
22
23	## Step 3 — Determine the Format
24
25	Different channels need different formats:
26
27	In-app notification: 1–2 sentences. CTA button. No context needed.
28	Email announcement: Subject line + 3–4 short paragraphs. Problem → Solution → How to access → CTA.
29	Slack/Discord message: Conversational tone. Brief. Include a visual or GIF if possible.
30	Blog post / changelog: Full narrative. 300–600 words. Problem, solution, how it works, what's next.
31	LinkedIn post: Conversational, first-person. Story-forward. Include a real example or quote.
32	Product Hunt post: Tagline + body. Includes what problem it solves, who it's for, and how to try it.
33
34	Ask which format(s) the user needs.
35
36	## Step 4 — Write the Announcement
37
38	For each format requested, write:
39
40	Subject/headline: The benefit, not the feature name. "Now you can [do X] without [pain Y]"
41
42	Opening: Acknowledge the user's struggle or the request. Show you've been listening.
43
44	What's new: Describe the feature in user terms. What does the user do? What happens? What outcome do they get?
45
46	Why it matters: One sentence connecting the feature to user impact.
47
48	How to access: Clear, specific instructions. Don't assume they'll find it.
49
50	What's next: Optional. If there's more coming in this area, hint at it — creates anticipation.
51
52	CTA: One clear action: "Try it now", "See it in action", "Give us feedback".
53
54	## Step 5 — Tone Calibration
55
56	Calibrate tone based on:
57	- Product stage (from memory): Early-stage = scrappy and warm. Growth-stage = confident and product-led. Scale = polished and authoritative.
58	- Primary persona (from memory): Technical users want precision. Non-technical users want reassurance. Enterprise stakeholders want reliability signals.
59	- Channel: Blog = editorial. Email = personal. Slack = casual. LinkedIn = professional-but-human.
60
61	## Step 6 — Output
62
63	Produce:
64	- Launch announcement in all requested formats
65	- A "don't forget" checklist: in-app tooltip? Help doc? Customer success heads-up? Support team briefed?
66	- Suggested send time if relevant

People who liked this also viewed

6 picks

Type