skills/ai-marketing-suite/skills/market-launch/SKILL.md
# Product/Service Launch Playbook Generator ## Skill Purpose Generate a complete, week-by-week launch playbook for any product, service, or feature launch. This skill produces a tactical plan with templates, checklists, email sequences, social posts, and metrics tracking -- everything needed to execute a successful launch. ## When to Use - User is planning to launch a new product, service, feature, or offering - User asks for a launch plan, go-to-market strategy, or launch checklist - User wan
npx skillsauth add kennyolofsson23-netizen/claude-code-config skills/ai-marketing-suite/skills/market-launchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a complete, week-by-week launch playbook for any product, service, or feature launch. This skill produces a tactical plan with templates, checklists, email sequences, social posts, and metrics tracking -- everything needed to execute a successful launch.
/market launch or /market launch <product description>Before generating the playbook, collect these inputs from the user (ask if not provided):
Select the primary launch strategy based on the user's context:
| Launch Type | Best For | Key Channel | Timeline | |---|---|---|---| | Product Hunt | SaaS, dev tools, consumer apps | Product Hunt + Twitter/X | 4-6 weeks prep | | Email List Launch | Course, info product, SaaS with existing list | Email | 6-8 weeks | | Social Media Launch | Consumer product, personal brand | Twitter/X, LinkedIn, Instagram | 4-6 weeks | | Paid Ads Launch | E-commerce, established product | Facebook/Google Ads | 2-4 weeks prep | | Community Launch | Niche product, developer tools | Reddit, Discord, Slack communities | 6-8 weeks | | Partner Launch | B2B, enterprise, marketplace | Partner channels | 8-12 weeks | | Hybrid Launch | Any high-stakes launch | Multi-channel coordinated | 8-12 weeks |
Objective: Lock in positioning, build assets, set up infrastructure.
Tasks:
Deliverables:
Objective: Build anticipation, grow waitlist, recruit beta testers.
Tasks:
Content Calendar (Weeks 3-4): | Day | Content Type | Channel | Theme | |---|---|---|---| | Mon | Problem-awareness post | LinkedIn/Twitter | Why this problem matters | | Tue | Behind-the-scenes | Instagram/Twitter | Show what you're building | | Wed | Educational content | Blog/LinkedIn | Teach something related to your space | | Thu | Social proof | Twitter/LinkedIn | Beta tester quote or result | | Fri | Teaser/countdown | All channels | Build anticipation for launch |
Deliverables:
Objective: Maximize anticipation, finalize assets, prep launch infrastructure.
Tasks:
Deliverables:
Objective: Execute the launch with maximum impact and coordinated effort.
Day-by-Day Breakdown:
Monday - Soft Launch / VIP Access:
Tuesday - Public Announcement:
Wednesday - Social Proof Push:
Thursday - Objection Handling:
Friday - Urgency and Scarcity:
Saturday/Sunday - Wrap Up:
Objective: Maintain momentum, collect feedback, plan next iteration.
Tasks:
Email 1: The Teaser (2 weeks before) Subject: Something big is coming... Purpose: Build anticipation Content: Hint at the product, share the problem it solves, tease the launch date. Don't reveal everything. CTA: "Stay tuned" or "Make sure you're on the list"
Email 2: The Reveal (1 week before) Subject: Here's what we've been building Purpose: Show the product, build desire Content: Reveal the product with screenshots/video. Share beta tester results. Announce launch date and any early bird offer. CTA: "Mark your calendar" or "Get notified on launch day"
Email 3: The Social Proof (3 days before) Subject: "[Beta Tester Name] got [Result] in [Timeframe]" Purpose: Prove it works Content: Feature 2-3 beta tester testimonials with specific results. Address the "does this actually work?" objection. CTA: "Be ready for [launch day]"
Email 4: The Launch (Day 1) Subject: It's live -- [Product Name] is here Purpose: Drive immediate action Content: Announce the launch. State the offer clearly. Include early bird pricing or bonus. Link directly to purchase/signup. CTA: "Get [Product] now" with primary button
Email 5: The Social Proof Follow-Up (Day 3) Subject: People are already seeing results Purpose: Convert through social proof Content: Share first-customer testimonials, screenshots of reactions, usage stats. Create FOMO. CTA: "Join [X] others who already [outcome]"
Email 6: The Objection Handler (Day 4) Subject: "But what if [common objection]?" Purpose: Address hesitations Content: List and answer top 3-5 objections. Include guarantee/risk reversal. Share FAQ. CTA: "Try it risk-free"
Email 7: The Urgency Close (Day 5-7) Subject: [X hours] left for [early bird / bonus / discount] Purpose: Drive final conversions with urgency Content: Remind of the deadline. Recap the value. Final testimonial. Clear, single CTA. CTA: "Last chance to get [offer]"
Post 1: After [X months/weeks] of building, I'm thrilled to announce [Product Name] is live.
[Product] helps [target audience] [achieve outcome] without [pain point].
Here's the story of why I built it (and what it can do for you):
[Thread emoji] 1/
Post 2: The problem: [Describe the problem in detail. Make it relatable.]
Post 3: The solution: [What your product does, in simple terms. Include screenshot or demo GIF.]
Post 4: Early results: [Beta tester results, specific numbers]
Post 5: What's included: [Key features as bullet points]
Post 6: Special launch offer: [Pricing, early bird deal, bonus]
Post 7: Try it now: [Link] [CTA]
I just launched [Product Name], and here's why it matters:
[1-2 sentences about the problem]
After [talking to X customers / spending Y months building / experiencing this problem myself], I realized [insight].
So I built [Product Name] to [specific outcome].
Early users are already seeing:
- [Result 1]
- [Result 2]
- [Result 3]
If you [target audience descriptor], I'd love for you to check it out:
[Link]
Special launch pricing available for the next [timeframe].
#relevant #hashtags
Image/Carousel: Product screenshots, before/after, or results graphic
Caption:
[Hook - first line that stops the scroll]
The problem: [1-2 sentences]
The solution: [1-2 sentences about your product]
The results: [specific outcomes from beta users]
Launch special: [offer details]
Link in bio to get started.
[Relevant hashtags - 15-20 for Instagram]
Press Release Structure:
Media Pitch Email Template:
Subject: [Angle] -- [Product Name] launches to [outcome]
Hi [Name],
I'm reaching out because you've covered [related topic] and I thought [Product Name] might be interesting for your readers.
[One sentence about what it does and why it's newsworthy]
[One sentence about early traction or results]
[One sentence about what makes it different]
I'd love to offer you [exclusive story / early access / founder interview / demo].
Happy to share more details if you're interested.
Best,
[Name]
Partner Outreach Timeline:
What to Provide Partners:
Track these metrics in real-time during launch week:
Awareness Metrics:
Engagement Metrics:
Conversion Metrics:
Retention Metrics (Post-Launch):
| Budget Level | Allocation | |---|---| | Bootstrapped ($0-500) | 100% organic: content, communities, email list, personal outreach | | Moderate ($500-5,000) | 40% paid ads, 30% influencer/partner, 20% tools/software, 10% design | | Well-Funded ($5,000-25,000) | 35% paid ads, 25% influencer/partner, 20% PR/media, 10% events, 10% tools | | Enterprise ($25,000+) | 30% paid ads, 20% events/webinars, 20% PR, 15% influencer, 10% content, 5% tools |
After the launch, generate a retrospective covering:
Generate a file called LAUNCH-PLAYBOOK.md with:
# Launch Playbook: [Product Name]
## Launch Date: [Date]
## Launch Type: [Type]
## Primary Goal: [Goal with specific target]
---
## Week-by-Week Plan
[Detailed week-by-week tasks with checkboxes]
## Email Sequences
[Complete email templates customized for the product]
## Social Media Content
[Platform-specific posts ready to customize and schedule]
## Partner/Influencer Plan
[Outreach templates and coordination timeline]
## Launch Day Checklist
[Hour-by-hour launch day plan]
## Metrics Dashboard
[Metrics to track with target benchmarks]
## Budget Allocation
[Specific dollar amounts based on stated budget]
## Post-Launch Plan
[Week 8+ activities and analysis framework]
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
testing
Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
development
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
development
Initialize a new project with Kenny's universal conventions and stack-appropriate infrastructure. Use this skill whenever: setting up a new project, creating a new repo, scaffolding a new app, starting fresh on a new idea, 'init project', 'new project', 'set up a new app', 'create a project for X', or any variant of starting a new codebase from scratch. Also trigger when the user says 'bootstrap', 'scaffold', or 'kickstart'. This skill ensures every project gets the same quality gates and conventions while adapting infrastructure to the chosen stack.