← ClaudeAtlas

feature-launch-playbooklisted

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.
gooseworks-ai/goose-skills · ★ 713 · AI & Automation · score 82
Install: claude install-skill gooseworks-ai/goose-skills
# 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 6. **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 7. **Launch date** — When does this go live? 8. **CTA** — What should the reader do? (Try it,