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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
Before generating assets, define the messaging foundation:
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]"
## [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]
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"]
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]
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]
Generate a launch checklist based on the tier:
Save all assets to the current working directory (or user-specified path) under a [feature-slug]/ folder:
launch-kit.md — All assets in one documentchecklist.md — Launch checklist with owner assignments| Component | Cost |
|---|---|
| All asset generation | Free (LLM reasoning) |
| Total | Free |
None. Pure reasoning skill. Works with any LLM agent.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a brand's facts, a campaign brief and the product into a one-minute Meta ad strategy with its reasoning — goal, audience, objective and placements, budget split, how many ads and how different they must be (generate 3x so the user can choose), the test frame, the success metric, and safety rules for the user to accept. Decides what launch-meta-ad-campaign then executes, and re-reads the strategy after a deep check to show which assumption changed. Use it after intake and before any creative is generated or any campaign is built.
日本語の概要は準備中です。原文の説明を表示しています。