| name | planning-product-launch |
| description | Creates go-to-market plans and launch checklists for features and side projects. Use when preparing a feature for public release, planning a Product Hunt launch, defining a rollout strategy, creating a post-launch review framework, or coordinating the technical, product, and marketing work for a launch. Triggers on: "prepare launch", "go-to-market", "Product Hunt", "launch checklist", "rollout plan", "launch this feature". |
Planning Product Launch
Core Philosophy
Launch is a process, not an event. Most launches fail not because the product is bad, but because the preparation was incomplete — monitoring wasn't in place, the rollback plan wasn't tested, or the messaging was unclear.
Every launch is a rehearsal for the next one. Document what happened and why so the process improves each time.
Workflow
Step 1 — GTM Brief
Define the narrative before any tactical work:
Feature: [Name]
Positioning sentence: For [audience], [feature] is a [category] that [key benefit], unlike [alternative].
Target audience: [specific segment — not "everyone"]
Core message: [one thing you want people to remember]
Key channels: [where this audience actually is]
Launch date: [date]
Success metric: [number that changes in 7 days if launch works]
The positioning sentence forces you to make choices. If you can't complete it, the feature scope is unclear and launch should wait.
Output: Top of docs/launches/YYYY-MM-DD-[feature]-launch.md
Step 2 — Technical Readiness Checklist
Verify before any external communication goes out:
Monitoring
