跳到正文
cccskills
免费在 GitHub 公开

feature-launch-playbook

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.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(2)

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

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

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

Launch Context

  1. 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
  2. Launch date — When does this go live?
  3. CTA — What should the reader do? (Try it, book a demo, read docs, upgrade)
  4. Visual assets available? — Screenshots, GIFs, demo video URL?

Tone & Voice

  1. Brand voice — Technical/developer, conversational/founder-led, enterprise/professional?
  2. 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]

Asset 5: In-App Banner / Notification

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

Asset 6: Internal Sales Enablement One-Pager (Tier 1 only)

# [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

ComponentCost
All asset generationFree (LLM reasoning)
TotalFree

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"

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Research supported advertising promises from a specific buyer's context, current product facts, customer language and observed ads. Turn them into static, video or copy ideas; match video ideas to actual recipes and save a product-scoped angle bank for write-video-ad-script. Product-led discovery can use verified facts without reviews. Reference persistence and reach are observations, not proof of performance.

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

Analyze ad campaign performance data (Google, Meta, LinkedIn) to identify what's working, what's wasting budget, and specific cut/scale/test recommendations. Runs statistical analysis, funnel diagnostics, and multi-channel budget reallocation with specific dollar-amount shift recommendations and scenario modeling.

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

For paid lead-gen and participant-recruitment ads, replaces vanity CPA with true CAC per qualified lead by joining ad-platform data with downstream funnel events, surfaces tracking gaps, and classifies every creative into Scale / Keep / Investigate / Cut.

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

The intake stage of a Meta ad harness. Researches the brand first, states what it assumes, and asks only what it cannot infer and what would change money, claims or legal exposure if guessed wrong — at most four questions a turn, in plain business language. Writes the brand's stable facts (ads/brand.md), the campaign brief, and a log of what was asked vs assumed. Use it when someone wants to run Meta ads and the brand's ad facts are not yet recorded.

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

Checks paid ads against the ad platform's rules (Meta, TikTok, Google, LinkedIn and others) and the brand's category rules: the copy, on-image or on-screen text, pictures and people. Rewrites what can be fixed honestly, adds the disclosures that are needed, and flags anything that needs a human or legal review, with one pass, fixed or flag line per ad and platform. Use alone when you already have the ad text or images and know where they will run; otherwise run the playbook for the job (e.g. make-static-ads, make-content, email-lifecycle).

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.

中文简介正在准备中。当前显示原文说明。

gooseworks-ai/goose-skills12652026年10月25日 更新

查看 gooseworks-ai 的全部技能

报告此技能的问题