launch-planning
Launch Planning
Plan launches that drive adoption, not just press releases.
How to use
/launch-planningApply launch planning constraints to this conversation./launch-planning <feature>Build a launch plan for the described feature or product.
Constraints
Launch Tiers
Not every launch deserves the same effort. Tier them:
- Tier 1 (big deal): new product, major feature, pricing change. Full cross-functional coordination.
- Tier 2 (notable): significant improvement, new integration. Blog post, email, in-app announcement.
- Tier 3 (incremental): bug fixes, small improvements. Changelog entry, maybe a tooltip.
- MUST assign a tier before planning. Over-launching small things causes announcement fatigue.
Pre-Launch
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1