api-integration
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs…
Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone.
$ npx -y skills add cwinvestments/memstack --skill launch-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/launch-planContext preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone.
name: memstack-marketing-launch-plan description: "Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone." version: 1.0.0 license: "Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt"
*Develops a day-by-day launch timeline with pre-launch buildup, launch week execution, post-launch optimization, channel strategy, PR outreach templates, and metrics tracking.*
When this skill activates, output:
`Launch Plan: Planning product launch...`
Then execute the protocol below.
| Context | Status | |---------|--------| | User says "launch plan", "product launch", "go-to-market" | ACTIVE | | User says "launch calendar" or "launch timeline" | ACTIVE | | User is preparing to release a new product or feature | ACTIVE | | User wants an ongoing sales funnel (not time-bound) | DORMANT: use Sales Funnel | | User wants ad copy only | DORMANT, use Facebook Ad or Google Ad |
| Mistake | Why It's Wrong | |---------|---------------| | "Launch day IS the marketing plan" | 80% of launch success happens in the pre-launch phase. The launch day is execution, not strategy. | | "Tell everyone at once" | Tiered reveals (insiders → waitlist → public) create momentum and social proof. | | "No deadline on the launch offer" | Open-ended launches have no urgency. Set a clear close date for the launch price/bonus. | | "Skip the waitlist" | A waitlist of 500+ people means launch day revenue, not crickets. | | "Go dark after launch day" | Post-launch follow-up (days 2-7) often generates more revenue than day 1. |
If the user hasn't provided details, ask:
> 1. **Product/service**: what are you launching? (name, description, price) > 2. **Launch date**: when does it go live? > 3. **Audience size**: email list, social followers, existing customers? > 4. **Launch type**: new product, major update, beta → GA, or seasonal promotion? > 5. **Channels**: email, social, ads, PR, partnerships, affiliates? > 6. **Launch offer**: special pricing, bonus, or early-bird deal?
| Launch Type | Pre-Launch | Launch Window | Post-Launch | |------------|-----------|--------------|-------------| | **Product Hunt launch** | 2-4 weeks | 1 day | 1 week | | **SaaS launch** | 4-6 weeks | 1 week | 2-4 weeks | | **Course/info product** | 2-4 weeks | 3-5 days (open cart) | 1 week | | **E-commerce product** | 2-3 weeks | 1-2 weeks | Ongoing | | **Feature launch** | 1-2 weeks | 1-3 days | 1 week |
**Week 4-3: Foundation**
| Day | Task | Channel | Owner | |-----|------|---------|-------| | T-28 | Finalize launch offer (pricing, bonuses, deadline) | Internal | Product | | T-27 | Create landing page with waitlist signup | Web | Marketing | | T-26 | Set up email sequences (pre-launch + launch) | Email | Marketing | | T-25 | Prepare PR/media list (50+ relevant contacts) | PR | Marketing | | T-24 | Create social content calendar (14 posts minimum) | Social | Content | | T-23 | Record demo video or product walkthrough | Video | Product | | T-22 | Brief affiliates/partners with swipe copy | Partners | Marketing |
**Week 2-1: Build Anticipation**
| Day | Task | Channel | Owner | |-----|------|---------|-------| | T-14 | Send teaser email #1, "Something's coming" | Email | Marketing | | T-12 | Behind-the-scenes social post (product development) | Social | Content | | T-10 | Send PR pitch to media list | PR | Marketing | | T-8 | Teaser email #2, reveal a feature/benefit | Email | Marketing | | T-7 | Publish blog post related to the problem you solve | Blog | Content | | T-5 | Social proof post (beta user testimonial or preview) | Social | Content | | T-3 | Teaser email #3, "Launching in 3 days" with preview | Email | Marketing | | T-2 | Notify affiliates/partners: "Go live in 48 hours" | Partners | Marketing | | T-1 | Final prep: test checkout, verify tracking, stage all content | Internal | All |
**Pre-launch email sequence:**
Email 1 (T-14): [Teaser] Subject: Something big is coming... Body: Hint at the problem you're solving. Don't reveal the product yet. CTA: "Want early access? Join the waitlist" Email 2 (T-8): [Reveal] Subject: Here's what we've been building Body: Show one key feature/benefit. Share the "why" story. CTA: "Reply and tell me: would this help you?" Email 3 (T-3): [Countdown] Subject: 3 days until launch (and a special deal) Body: Reveal the launch offer. Create urgency with deadline. CTA: "Mark your calendar: [launch date] at [time]"
**Day 1: Launch Day:**
| Time | Task | Channel | |------|------|---------| | 6:00 AM | Activate landing page / checkout | Web | | 7:00 AM | Send launch email to full list | Email | | 8:00 AM | Publish all social posts (feed + stories) | Social | | 9:00 AM | Go live on Product Hunt (if applicable) | PH | | 10:00 AM | Activate paid ads (if planned) | Ads | | 12:00 PM | Share in communities (Reddit, Slack, Discord) | Community | | 3:00 PM | Send affiliate notification: "We're live!" | Partners | | 6:00 PM | Evening social post: first results/reactions | Social | | 9:00 PM | Check metrics: traffic, signups, revenue | Analytics |
**Launch email template:**
Subject: It's live, [Product Name] is here Preview: [One-line benefit + launch offer] [Name], [Product] is officially live. [1-2 sentences: what it is and who it's for] Here's what you get: → [Benefit 1] → [Benefit 2] → [Benefit 3] Launch special: [Offer details: discount, bonus, early-bird price] This offer expires [deadline]. [CTA Button: Get [Product] Now →] [Social proof: "Already [X] people signed up in the first hour"] [S
The structured skill framework for Claude Code: 131 professional skills for deployment, security, databases, content, marketing, and more. Skills activate automatically when you need them. Say "deploy this to Railway" and the right skill loads on demand.
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs…
Use this skill when the user says 'content pipeline', 'content automation', 'auto-publish', 'repurpose content', 'multi-platform…
Use this skill when the user says 'cron job', 'scheduled task', 'run every', 'cron expression', 'recurring job', or needs…
Use when the user says 'what MCP servers', 'find an MCP for', 'hosted MCP', 'list MCP servers', 'MCP catalog', 'available MCP…
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual…
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification',…