Market LaunchSAFE

AI Marketing Suite for Claude Code. 15 marketing skills with parallel subagents — audit any website, generate copy, email sequences, ad campaigns, content calendars, competitive intelligence, and client-ready PDF reports.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

# 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 wants to coordinate a multi-channel launch campaign
- Triggered by `/market launch` or `/market launch <product description>`

## How to Execute

### Step 1: Gather Launch Context
Before generating the playbook, collect these inputs from the user (ask if not provided):

1. **What are you launching?** (product, service, feature, course, event)
2. **Who is the target audience?** (demographics, pain points, existing list size)
3. **What is the primary launch goal?** (revenue target, signups, downloads, awareness)
4. **What is the launch date?** (or desired timeline)
5. **What channels do you have access to?** (email list size, social following, ad budget, partnerships)
6. **What is the price point?** (if applicable)
7. **Do you have existing customers/users?** (for beta, testimonials, case studies)
8. **What is the budget?** (bootstrapped, moderate, well-funded)

### Step 2: Determine Launch Type
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 |

### Step 3: Generate the 8-Week Launch Timeline

#### Weeks 1-2: Foundation
**Objective:** Lock in positioning, build assets, set up infrastructure.

**Tasks:**
- [ ] Define launch positioning statement: "For [TARGET] who [PROBLEM], [PRODUCT] is a [CATEGORY] that [KEY BENEFIT]. Unlike [ALTERNATIVE], we [DIFFERENTIATOR]."
- [ ] Create launch one-pager (internal alignment doc)
- [ ] Set up landing page / waitlist page
- [ ] Set up analytics and tracking (UTM parameters, conversion goals, event tracking)
- [ ] Create launch-specific email list/segment
- [ ] Draft all email sequences (see Email Templates below)
- [ ] Brief design team on visual assets needed
- [ ] Identify 10-20 potential beta testers or early access users
- [ ] Research and list 20+ communities, forums, and groups where target audience gathers
- [ ] Set up social media content calendar tool

**Deliverables:**
- Positioning statement
- Landing page live
- Email sequences drafted
- Beta tester list

#### Weeks 3-4: Audience Building
**Objective:** Build anticipation, grow waitlist, recruit beta testers.

**Tasks:**
- [ ] Begin content seeding: publish 2-3 blog posts / threads related to the problem you solve
- [ ] Share behind-the-scenes content on social media (building in public)
- [ ] Start engaging in target communities (provide value, don't pitch yet)
- [ ] Reach out to beta testers with personal invitations
- [ ] Collect early feedback and testimonials from beta users
- [ ] Begin influencer/partner outreach (see Partner Coordination below)
- [ ] Set up referral mechanism for waitlist (e.g., viral waitlist with rewards)
- [ ] Create teaser content (sneak peeks, countdowns, problem-awareness posts)
- [ ] Record demo video or product walkthrough
- [ ] Write press release or media pitch (if relevant)

**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:**
- 4-6 content pieces published
- Beta testers onboarded and providing feedback
- Waitlist growing
- Partner/influencer commitments secured

#### Weeks 5-6: Pre-Launch Intensification
**Objective:** Maximize anticipation, finalize assets, prep launch infrastructure.

**Tasks:**
- [ ] Send pre-launch email sequence to waitlist (see Email Templates)
- [ ] Increase social media posting frequency to daily
- [ ] Publish case study or results from beta testers
- [ ] Finalize pricing and offer structure
- [ ] Create launch-day content package (all posts, emails, and graphics ready)
- [ ] Brief partners/affiliates on launch plan and provide swipe copy
- [ ] Set up live chat or support for launch day
- [ ] Test all purchase/signup flows end-to-end
- [ ] Prepare FAQ document for support team
- [ ] Create urgency mechanism (early bird pricing, limited spots, bonus expiration)
- [ ] Rehearse launch day by walking through every step
- [ ] Set up real-time dashboard for launch metrics

**Deliverables:**
- All launch assets finalized and scheduled
- Partners briefed and ready
- Checkout/signup flow tested
- Support team prepared

#### Week 7: LAUNCH WEEK
**Objective:** Execute the launch with maximum impact and coordinated effort.

**Day-by-Day Breakdown:**

**Monday - Soft Launch / VIP Access:**
- Send early access email to VIPs, beta testers, and top waitlist members
- Post on social: "We're live for our early supporters"
- Collect first-day feedback and testimonials
- Monitor for bugs and issues
- Goal:

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (1)

Gates applied: no_behavioural_pass.