{
    "slug": "launch",
    "name": "launch",
    "description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'site launch,' 'go live,' 'pre-launch QA,' 'launch checklist,' 'GTM plan,' 'we're about to ship,' 'changelog,' 'release notes,' or 'what did we ship this week.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.",
    "frontmatter": {
        "name": "launch",
        "description": "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'site launch,' 'go live,' 'pre-launch QA,' 'launch checklist,' 'GTM plan,' 'we're about to ship,' 'changelog,' 'release notes,' or 'what did we ship this week.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.",
        "metadata": "",
        "version": "2.2.0"
    },
    "body": "# Launch Strategy\n\nYou are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n\nThe best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.\n\nA strong launch isn't about a single moment. It's about:\n- Getting your product into users' hands early\n- Learning from real feedback\n- Making a splash at every stage\n- Building momentum that compounds over time\n\n---\n\n## The ORB Framework\n\nStructure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.\n\n### Owned Channels\nYou own the channel (though not the audience). Direct access without algorithms or platform rules.\n\n**Examples:**\n- Email list\n- Blog\n- Podcast\n- Branded community (Slack, Discord)\n- Website/product\n\n**Why they matter:**\n- Get more effective over time\n- No algorithm changes or pay-to-play\n- Direct relationship with audience\n- Compound value from content\n\n**Start with 1-2 based on audience:**\n- Industry lacks quality content → Start a blog\n- People want direct updates → Focus on email\n- Engagement matters → Build a community\n\n**Example - Superhuman:**\nBuilt demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.\n\n### Rented Channels\nPlatforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.\n\n**Examples:**\n- Social media (Twitter/X, LinkedIn, Instagram)\n- App stores and marketplaces\n- YouTube\n- Reddit\n\n**How to use correctly:**\n- Pick 1-2 platforms where your audience is active\n- Use them to drive traffic to owned channels\n- Don't rely on them as your only strategy\n\n**Example - Notion:**\nHacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.\n\n**Platform-specific tactics:**\n- Twitter/X: Threads that spark conversation → link to newsletter\n- LinkedIn: High-value posts → lead to gated content or email signup\n- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more\n\nRented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.\n\n### Borrowed Channels\nTap into someone else's audience to shortcut the hardest part—getting noticed.\n\n**Examples:**\n- Guest content (blog posts, podcast interviews, newsletter features)\n- Collaborations (webinars, co-marketing, social takeovers)\n- Speaking engagements (conferences, panels, virtual summits)\n- Influencer partnerships\n\n**Be proactive, not passive:**\n1. List industry leaders your audience follows\n2. Pitch win-win collaborations\n3. Use tools like SparkToro or Listen Notes to find audience overlap\n4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/introw.md) to manage deal registration and commissions)\n\n**Example - TRMNL:**\nSent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.\n\nBorrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.\n\n---\n\n## Readiness Gate: Are You Ready to Launch?\n\nRun this **before** the phased mechanics. Products don't market themselves—but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching.\n\nTwo failure modes kill launches from opposite ends:\n\n- **Stealth Mode** — launching too late. \"Procrastination in a fancy suit.\" You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist.\n- **\"Just One More Feature\"** — never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes.\n\nThe middle path is **SLC — Simple, Lovable, Complete** (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is:\n\n- **Simple** — it does *one* thing. Not many things poorly. One clear job, done well.\n- **Lovable** — people *want* to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience \"to give feedback.\" SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet.\n- **Complete** — it's a *whole* experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise.\n\n**The gate:** If it's not yet Simple, Lovable, and Complete, you're in \"Just One More Feature\" territory only when adding scope is what's missing—otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never.\n\n**Quick check before running the phases:**\n- [ ] Does it do one clearly-defined thing? (Simple)\n- [ ] Would a target user *choose* to use it, not just endure it? (Lovable)\n- [ ] Is that one thing a whole experience, with no glaring stubs? (Complete)\n- [ ] Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship.\n- [ ] Are you still adding new things to the scope? → Stop. You're in \"Just One More Feature.\" Cut back to SLC.\n\nPass the gate, then run the phases below.\n\n---\n\n## Five-Phase Launch Approach\n\nLaunching isn't a one-day event. It's a phased process that builds momentum.\n\n### Phase 1: Internal Launch\nGather initial feedback and iron out major issues before going public.\n\n**Actions:**\n- Recruit early users one-on-one to test for free\n- Collect feedback on usability gaps and missing features\n- Ensure prototype is functional enough to demo (doesn't need to be production-ready)\n\n**Goal:** Validate core functionality with friendly users.\n\n### Phase 2: Alpha Launch\nPut the product in front of external users in a controlled way.\n\n**Actions:**\n- Create landing page with early access signup form\n- Announce the product exists\n- Invite users individually to start testing\n- MVP should be working in production (even if still evolving)\n\n**Goal:** First external validation and initial waitlist building.\n\n### Phase 3: Beta Launch\nScale up early access while generating external buzz.\n\n**Actions:**\n- Work through early access list (some free, some paid)\n- Start marketing with teasers about problems you solve\n- Recruit friends, investors, and influencers to test and share\n\n**Consider adding:**\n- Coming soon landing page or waitlist\n- \"Beta\" sticker in dashboard navigation\n- Email invites to early access list\n- Early access toggle in settings for experimental features\n\n**Goal:** Build buzz and refine product with broader feedback.\n\n### Phase 4: Early Access Launch\nShift from small-scale testing to controlled expansion.\n\n**Actions:**\n- Leak product details: screenshots, feature GIFs, demos\n- Gather quantitative usage data and qualitative feedback\n- Run user research with engaged users (incentivize with credits)\n- Optionally run product/market fit survey to refine messaging\n\n**Expansion options:**\n- Option A: Throttle invites in batches (5-10% at a time)\n- Option B: Invite all users at once under \"early access\" framing\n\n**Goal:** Validate at scale and prepare for full launch.\n\n### Phase 5: Full Launch\nOpen the floodgates.\n\n**Actions:**\n- Open self-serve signups\n- Start charging (if not already)\n- Announce general availability across all channels\n\n**Launch touchpoints:**\n- Customer emails\n- In-app popups and product tours\n- Website banner linking to launch assets\n- \"New\" sticker in dashboard navigation\n- Blog post announcement\n- Social posts across platforms\n- Product Hunt, BetaList, Hacker News, etc.\n\n**Goal:** Maximum visibility and conversion to paying users.\n\n---\n\n## Product Hunt Launch Strategy\n\nProduct Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.\n\n### Pros\n- Exposure to tech-savvy early adopter audience\n- Credibility bump (especially if Product of the Day)\n- Potential PR coverage and backlinks\n\n### Cons\n- Very competitive to rank well\n- Short-lived traffic spikes\n- Requires significant pre-launch planning\n\n### How to Launch Successfully\n\n**Before launch day:**\n1. Build relationships with influential supporters, content hubs, and communities\n2. Optimize your listing: compelling tagline, polished visuals, short demo video\n3. Study successful launches to identify what worked\n4. Engage in relevant communities—provide value before pitching\n5. Prepare your team for all-day engagement\n\n**On launch day:**\n1. Treat it as an all-day event\n2. Respond to every comment in real-time\n3. Answer questions and spark discussions\n4. Encourage your existing audience to engage\n5. Direct traffic back to your site to capture signups\n\n**After launch day:**\n1. Follow up with everyone who engaged\n2. Convert Product Hunt traffic into owned relationships (email signups)\n3. Continue momentum with post-launch content\n\n### Case Studies\n\n**SavvyCal** (Scheduling tool):\n- Optimized landing page and onboarding before launch\n- Built relationships with productivity/SaaS influencers in advance\n- Responded to every comment on launch day\n- Result: #2 Product of the Month\n\n**Reform** (Form builder):\n- Studied successful launches and applied insights\n- Crafted clear tagline, polished visuals, demo video\n- Engaged in communities before launch (provided value first)\n- Treated launch as all-day engagement event\n- Directed traffic to capture signups\n- Result: #1 Product of the Day\n\n---\n\n## Post-Launch Product Marketing\n\nYour launch isn't over when the announcement goes live. Now comes adoption and retention work.\n\n### Immediate Post-Launch Actions\n\n**Educate new users:**\nSet up automated onboarding email sequence introducing key features and use cases.\n\n**Reinforce the launch:**\nInclude announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.\n\n**Differentiate against competitors:**\nPublish comparison pages highlighting why you're the obvious choice.\n\n**Update web pages:**\nAdd dedicated sections about the new feature/product across your site.\n\n**Offer hands-on preview:**\nCreate no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.\n\n### Keep Momentum Going\nIt's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.\n\n---\n\n## Ongoing Launch Strategy\n\nDon't rely on a single launch event. Regular updates and feature rollouts sustain engagement.\n\n### How to Prioritize What to Announce\n\nUse this matrix to decide how much marketing each update deserves:\n\n**Major updates** (new features, product overhauls):\n- Full campaign across multiple channels\n- Blog post, email campaign, in-app messages, social media\n- Maximize exposure\n\n**Medium updates** (new integrations, UI enhancements):\n- Targeted announcement\n- Email to relevant segments, in-app banner\n- Don't need full fanfare\n\n**Minor updates** (bug fixes, small tweaks):\n- Changelog and release notes\n- Signal that product is improving\n- Don't dominate marketing\n\n### Announcement Tactics\n\n**Space out releases:**\nInstead of shipping everything at once, stagger announcements to maintain momentum.\n\n**Reuse high-performing tactics:**\nIf a previous announcement resonated, apply those insights to future updates.\n\n**Keep engaging:**\nContinue using email, social, and in-app messaging to highlight improvements.\n\n**Signal active development:**\nEven small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.\n\n**Turn shipped code into announcements:**\nIf you can read the product repo, generate the week's changelog, announcement drafts, and pages-to-update list straight from merged PRs. See [references/shipped-changes.md](references/shipped-changes.md).\n\n---\n\n## Launch Checklist\n\n### Pre-Launch\n- [ ] Landing page with clear value proposition\n- [ ] Email capture / waitlist signup\n- [ ] Early access list built\n- [ ] Owned channels established (email, blog, community)\n- [ ] Rented channel presence (social profiles optimized)\n- [ ] Borrowed channel opportunities identified (podcasts, influencers)\n- [ ] Product Hunt listing prepared (if using)\n- [ ] Launch assets created (screenshots, demo video, GIFs)\n- [ ] Onboarding flow ready\n- [ ] Analytics/tracking in place\n- [ ] Site QA done if the launch includes a new site, redesign, or migration (see [references/site-launch-qa.md](references/site-launch-qa.md))\n\n### Launch Day\n- [ ] Announcement email to list\n- [ ] Blog post published\n- [ ] Social posts scheduled and posted\n- [ ] Product Hunt listing live (if using)\n- [ ] In-app announcement for existing users\n- [ ] Website banner/notification active\n- [ ] Team ready to engage and respond\n- [ ] Monitor for issues and feedback\n\n### Post-Launch\n- [ ] Onboarding email sequence active\n- [ ] Follow-up with engaged prospects\n- [ ] Roundup email includes announcement\n- [ ] Comparison pages published\n- [ ] Interactive demo created\n- [ ] Gather and act on feedback\n- [ ] Plan next launch moment\n\n---\n\n## Task-Specific Questions\n\n1. What are you launching? (New product, major feature, minor update)\n2. What's your current audience size and engagement?\n3. What owned channels do you have? (Email list size, blog traffic, community)\n4. What's your timeline for launch?\n5. Have you launched before? What worked/didn't work?\n6. Are you considering Product Hunt? What's your preparation status?\n\n---\n\n## Related Skills\n\n- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)\n- **emails**: For launch and onboarding email sequences\n- **cro**: For optimizing launch landing pages\n- **marketing-psychology**: For psychology behind waitlists and exclusivity\n- **programmatic-seo**: For comparison pages mentioned in post-launch\n- **sales-enablement**: For launch sales collateral and enablement materials\n",
    "references": {
        "shipped-changes.md": {
            "name": "Shipped Changes",
            "path": "shipped-changes.md",
            "content": "# From Shipped Code to Marketing\n\nMost product updates never get marketed because nobody translates them. The engineers wrote the PR description for each other, and by the time marketing hears about it, the moment has passed. An agent with access to the repo can close that gap every week: read what shipped, decide what's worth telling, and draft it in customer language.\n\n## Inputs\n\nFor the chosen window (usually the last week, or since the last release tag):\n- **Merged PRs** with titles, descriptions, and linked issues. These explain *why* better than commits do.\n- **Commit log** for anything merged without a PR: `git log --since=\"1 week ago\" --no-merges --pretty=format:\"%h %s (%an, %ar)\"`\n- **Changed files**, read wherever a title doesn't make the user-facing effect clear.\n- **Release notes or tags**, if the team already writes them.\n- **Feature flags**: what's actually live for customers versus merged behind a flag.\n\nOnly market what customers can use today. Anything behind a flag, in internal beta, or not yet deployed waits.\n\n## Translate before you write\n\nEngineering changes are described by what changed in the code. Customers care about what changed for them. For each change, write one line: **\"You can now ___\"** or **\"___ no longer ___.\"** If you can't fill that in, the change is invisible to customers. Refactors, dependency bumps, CI, and test changes go in no marketing output at all.\n\nThen group the visible changes with the tiers in the Ongoing Launch Strategy section of `SKILL.md`:\n\n| Tier | Typical changes | Output |\n|------|-----------------|--------|\n| **Major** | New capability, new plan, big workflow change | Changelog + blog post + email + social + in-app |\n| **Medium** | New integration, notable UX improvement, performance gain customers can feel | Changelog + targeted email or in-app + one social post |\n| **Minor** | Fixes, polish, small additions | Changelog only, batched |\n\nSeveral medium changes that share a theme (\"five improvements to reporting\") can be bundled into one major-tier story.\n\n## Ground every claim in the change\n\n- State what the change does, not what it might do for someone. \"Exports now include custom fields,\" not \"unlock deeper insights.\"\n- Use numbers only if they come from the change itself (a benchmark in the PR, a measured speedup). Never invent customer results, adoption, or impact.\n- If a PR says the change is partial (\"phase 1,\" \"first step toward\"), the announcement says so too.\n- Credit the user who asked for it, where the team does that and the user agreed.\n\n## Watch for marketing that just became wrong\n\nEvery shipped change can also make an existing claim false: a new limit, a renamed plan, a removed integration, a price change. Check the site, docs, comparison pages, and ads for statements the change contradicts. On a schedule, this is the claim-drift loop in `marketing-loops`.\n\nNew capabilities also open new search demand. A new integration can deserve its own page (\"[Product] + [Tool] integration\"), and a new feature can answer queries or comparisons the product couldn't win before. Add those to the content backlog (see `content-strategy` and `competitors`).\n\n## Weekly digest format\n\n```markdown\n## Shipped: [date range]\n\n### For customers\n- **[Major]** [You can now ...] (PR #123)\n- **[Medium]** [You can now ...] (PR #130)\n- **[Minor]** [Fixed ...] (PR #131, #134)\n\n### Changelog entry\n## [version or date]\n### Added\n- [Customer-facing description]\n### Changed\n- [...]\n### Fixed\n- [...]\n\n### Drafts\n- Blog post: [working title], [angle], [who it's for]\n- Email: [subject line options] → [segment]\n- Social: [one post per major or medium change, built on its single most useful detail]\n- In-app: [message + where it appears]\n\n### Pages to update\n- [Page]: [statement that's now wrong or incomplete]\n\n### New content opportunities\n- [Query or comparison the change makes winnable]\n```\n\nUse Keep a Changelog headings (Added, Changed, Deprecated, Removed, Fixed, Security) so the changelog stays scannable over time.\n\n## Writing the drafts\n\n- **Changelog:** one line per change, written for a customer and in past or present tense. Link docs for anything non-obvious.\n- **Blog post (major only):** the problem the customer had, what changed, how to use it (with screenshots), and who it's for. The `copywriting` skill covers structure; its AI-tell rules apply.\n- **Email:** lead with the change for that segment; one call to action that takes them to the feature. See `emails`.\n- **Social:** one concrete detail per post, with a screenshot or 10-second clip of the feature doing it. See `social`.\n\nDrafts are staged for a human to review and send. Nothing in this workflow publishes on its own.\n"
        },
        "site-launch-qa.md": {
            "name": "Site Launch Qa",
            "path": "site-launch-qa.md",
            "content": "# Site Launch QA\n\nThe checks to run before and right after a website goes live: a new site, a redesign, a platform migration, or a big new section. Product launches fail quietly when the site underneath them breaks, and most of these failures are invisible from the homepage.\n\nRun it in three passes: before the switch, at the switch, and in the first two weeks after.\n\n## Before the switch\n\n**Content and links**\n- [ ] Every page in the plan exists, with final copy (no lorem ipsum, \"TBD,\" or test prices)\n- [ ] Crawl the staging site for broken internal links and missing images\n- [ ] Legal pages (privacy, terms, cookie policy) are present and current\n- [ ] Contact details, pricing, and plan names match what sales and support say\n\n**Forms and conversions**\n- [ ] Submit every form with a test entry and confirm it reaches the inbox, CRM, or tool it should\n- [ ] Confirmation messages and redirects work, and spam protection doesn't block real submissions\n- [ ] Conversion tracking fires on the confirmed submission, not the button click (the `conversion-tracking` skill covers the setup and the test)\n- [ ] Analytics is installed once, on every page, with internal traffic filtered\n- [ ] Consent banner works and tags respect it\n\n**SEO**\n- [ ] Every page has a unique title, meta description, and one H1\n- [ ] Canonical tags point to the production domain, not staging\n- [ ] Staging is `noindex` or password-protected, and production is **not** (the most common launch-day SEO failure is shipping the staging `noindex`)\n- [ ] `robots.txt` allows the pages you want indexed; the XML sitemap lists production URLs\n- [ ] Structured data validates (Rich Results Test for Google features, Schema Markup Validator for everything else)\n- [ ] For a migration: the redirect map is loaded and tested on a sample of old URLs (see the `site-architecture` skill's platforms and migration reference)\n\n**Performance and access**\n- [ ] Core Web Vitals are acceptable on the key templates, on mobile\n- [ ] Pages work on mobile, in Safari, and inside in-app browsers (LinkedIn, Instagram, Facebook)\n- [ ] Images have alt text; forms have labels; keyboard navigation works\n- [ ] Open Graph images and titles render correctly when the URL is shared\n\n**Rollback**\n- [ ] You know how to roll back on this platform, and someone has done it once. Examples: Vercel and Netlify promote a previous deployment; Webflow restores a site backup; WordPress restores from a backup plugin or host snapshot; Ploy ◆ promotes a previous deploy from its Deploys screen (its CLI always publishes to production, with no staging target, so preview before publishing).\n- [ ] DNS TTL lowered a day ahead if the switch involves DNS changes\n\n◆ marks a [Verified Partner](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md#verified-partners) of this repository: disclosure, not endorsement.\n\n## At the switch\n\n- [ ] Deploy redirects at the same moment as the new site\n- [ ] Confirm HTTPS works on every hostname (`www` and apex) and one redirects to the other\n- [ ] Load the top 10 pages by traffic and check content, title, canonical, and a 200 status\n- [ ] Submit one real form and confirm it arrives everywhere it should\n- [ ] Submit the sitemap in Search Console and Bing Webmaster Tools\n- [ ] Re-check that production isn't `noindex`\n\n## The first two weeks\n\n- [ ] Search Console: watch coverage and 404s daily for the first week, then weekly; fix missing redirects as they show up\n- [ ] Compare traffic and conversions to the same period before, page by page, not just in total\n- [ ] Confirm conversions are arriving in each ad platform at the expected rate\n- [ ] Fix internal links that still point at redirected URLs\n- [ ] Collect the bugs the team and customers report, and decide what's urgent\n"
        }
    },
    "evals": {
        "skill_name": "launch",
        "evals": [
            {
                "id": 1,
                "prompt": "We're launching a new B2B SaaS product for design teams in 6 weeks. It's a design review tool. We have a small audience (500 email subscribers, 2k Twitter followers). Help us plan the launch.",
                "expected_output": "Should check for product-marketing.md first. Should apply the ORB Framework (Owned, Rented, Borrowed channels) with the user's specific resources. Owned: email list (500 subscribers), website. Rented: Twitter (2k followers). Borrowed: partnerships, communities, Product Hunt. Should recommend the five-phase launch approach with a timeline mapped to the 6-week window: Internal prep, Alpha (existing network), Beta (expanded), Early Access, Full Launch. Should provide specific tactics for each phase. Should recommend building up the audience before launch day. Should include a launch day checklist.",
                "assertions": [
                    "Checks for product-marketing.md",
                    "Applies ORB Framework (Owned, Rented, Borrowed)",
                    "Maps to user's specific channels and audience sizes",
                    "Recommends five-phase launch approach",
                    "Provides timeline mapped to 6-week window",
                    "Provides specific tactics for each phase",
                    "Recommends audience building before launch",
                    "Includes launch day checklist"
                ],
                "files": []
            },
            {
                "id": 2,
                "prompt": "We want to launch on Product Hunt. Any tips? We've never done it before.",
                "expected_output": "Should apply the Product Hunt strategy section. Should cover: choosing the right day and time, preparing assets (logo, gallery images, maker video), crafting the tagline and description, building a hunter network, activating supporters on launch day, engaging with comments, and post-launch follow-up. Should recommend preparation timeline (start 2-4 weeks before). Should mention common mistakes to avoid. Should set realistic expectations about outcomes.",
                "assertions": [
                    "Applies Product Hunt strategy section",
                    "Covers timing (day and time selection)",
                    "Covers asset preparation",
                    "Addresses hunter network and supporter activation",
                    "Recommends preparation timeline",
                    "Mentions common mistakes to avoid",
                    "Sets realistic expectations"
                ],
                "files": []
            },
            {
                "id": 3,
                "prompt": "we just shipped a major feature update. how should we announce it? it's not a full product launch, just a big new feature.",
                "expected_output": "Should trigger on casual phrasing. Should apply the ongoing launch strategy section, specifically the major/medium/minor update matrix. Should identify this as a major feature update. Should recommend appropriate channels and tactics for a feature launch (less than a full product launch but more than a changelog entry). Should include: announcement email, blog post, social media push, in-app notification, and possibly a mini Product Hunt launch. Should provide a feature announcement framework.",
                "assertions": [
                    "Triggers on casual phrasing",
                    "Applies ongoing launch strategy / update matrix",
                    "Identifies as major feature update",
                    "Scales tactics appropriately (not full launch)",
                    "Recommends announcement channels",
                    "Includes email, blog, social, and in-app notification",
                    "Provides feature announcement framework"
                ],
                "files": []
            },
            {
                "id": 4,
                "prompt": "Our launch flopped. We launched 3 weeks ago and only got 50 signups. We expected at least 500. What went wrong and what can we do now?",
                "expected_output": "Should apply the post-launch product marketing section. Should diagnose potential failure causes: insufficient audience building pre-launch, wrong channels, weak value proposition messaging, poor launch execution, targeting the wrong audience. Should recommend post-launch recovery tactics: iterate on messaging, identify which channels produced the 50 signups and double down, try new distribution channels, leverage early users for testimonials. Should provide a specific 30-day recovery plan.",
                "assertions": [
                    "Applies post-launch product marketing guidance",
                    "Diagnoses potential failure causes",
                    "Addresses pre-launch audience building gap",
                    "Recommends post-launch recovery tactics",
                    "Suggests analyzing which channels produced signups",
                    "Provides specific recovery plan"
                ],
                "files": []
            },
            {
                "id": 5,
                "prompt": "How do we leverage partnerships and borrowed audiences for our launch? We don't have a big audience of our own.",
                "expected_output": "Should focus on the Borrowed channel from the ORB Framework. Should provide specific borrowed audience tactics: podcast guest appearances, co-marketing with complementary tools, influencer partnerships, community engagement (relevant Slack groups, Discord servers, Reddit), guest posts, cross-promotions. Should recommend how to identify and approach potential partners. Should note that borrowed audience strategies take time to build and should start well before launch day.",
                "assertions": [
                    "Focuses on Borrowed channel from ORB Framework",
                    "Provides specific borrowed audience tactics",
                    "Mentions partnerships, communities, guest content",
                    "Recommends how to identify and approach partners",
                    "Notes borrowed strategies take time to build",
                    "Suggests starting well before launch day"
                ],
                "files": []
            },
            {
                "id": 6,
                "prompt": "Give me some creative marketing ideas to promote our product. We're bootstrapped and don't have a big budget.",
                "expected_output": "Should recognize this is a broader marketing ideas request, not specifically a launch strategy task. Should defer to or cross-reference the marketing-ideas skill, which provides 139 marketing ideas organized by category and filtered by budget. May provide some launch-related tactical ideas but should make clear that marketing-ideas is the right skill for a broader brainstorming session.",
                "assertions": [
                    "Recognizes this as broader marketing ideas request",
                    "References or defers to marketing-ideas skill",
                    "Does not attempt full marketing brainstorm using launch strategy patterns",
                    "May provide some launch-related tactical ideas"
                ],
                "files": []
            },
            {
                "id": 7,
                "prompt": "We've been building our product in private for 8 months and keep pushing the launch date because there's always one more feature we want to add first. How do we know when we're actually ready to launch?",
                "expected_output": "Should apply the Readiness Gate before jumping to launch mechanics. Should name the two failure modes: Stealth Mode (launching too late, 'procrastination in a fancy suit') and 'Just One More Feature' (never launching), and identify that this user is exhibiting both. Should introduce SLC (Simple, Lovable, Complete) by Jason Cohen as the middle path and the alternative to a bare MVP. Should explain each: Simple (does one thing), Lovable (users want to use it, not just tolerate it), Complete (a whole experience, not a stub). Should advise cutting scope to reach SLC on one thing rather than adding more features, and to ship once the gate is passed. Should not just dump the five-phase mechanics without addressing readiness first.",
                "assertions": [
                    "Applies the readiness gate before launch mechanics",
                    "Names Stealth Mode and 'Just One More Feature' failure modes",
                    "Diagnoses the user as stuck in these failure modes",
                    "Introduces SLC (Simple, Lovable, Complete) as the middle path vs a bare MVP",
                    "Explains Simple, Lovable, and Complete distinctly",
                    "Advises cutting scope to reach SLC rather than adding features",
                    "Recommends shipping once the gate is passed"
                ],
                "files": []
            },
            {
                "id": 8,
                "prompt": "Our redesigned marketing site goes live Thursday on a new platform. What should we check before and after we flip the switch?",
                "expected_output": "Should load the site launch QA reference and give a before/at/after checklist: forms reach their destinations and conversion tracking fires on confirmed submission; unique titles, canonicals to production, staging noindex not shipped to production, robots and sitemap; redirect map loaded for changed URLs; mobile, Safari and in-app browser checks; Core Web Vitals; a known, practiced rollback for their platform; at switch, HTTPS on all hostnames, top pages return 200, real form test, sitemap submitted; after, daily Search Console 404 checks and page-level traffic comparison.",
                "assertions": [
                    "Checks forms and conversion tracking on confirmed submission",
                    "Warns about shipping the staging noindex",
                    "Includes the redirect map for changed URLs",
                    "Includes a practiced rollback plan",
                    "Includes post-launch Search Console monitoring"
                ],
                "files": []
            },
            {
                "id": 9,
                "prompt": "You have access to our product repo. Can you look at what we merged this week and turn it into a changelog entry and some announcement drafts?",
                "expected_output": "Should load the shipped-changes reference. Should read merged PRs (and the commit log for anything without a PR) for the week, exclude anything behind a feature flag or not deployed, and drop invisible changes like refactors, dependency bumps and CI. Should translate each visible change into a 'You can now...' line, tier it as major, medium or minor using the skill's announcement matrix, and produce a changelog entry using Keep a Changelog headings plus drafts matched to tier. Every claim should come from the change itself with no invented metrics or customer results. Should also list marketing pages the changes made wrong and new content opportunities, and stage all drafts for human review rather than publishing.",
                "assertions": [
                    "Reads merged PRs and commits for the window",
                    "Excludes flagged, undeployed and invisible changes",
                    "Translates changes into customer-facing 'You can now' statements",
                    "Tiers changes and matches output to the tier",
                    "Uses Keep a Changelog headings",
                    "Does not invent metrics or customer outcomes",
                    "Flags existing pages the changes made inaccurate",
                    "Stages drafts for review instead of publishing"
                ],
                "files": []
            }
        ]
    },
    "exported_at": "2026-10-12T10:26:53+02:00"
}