autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
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
$ npx -y skills add MaximoCorrea1/ultra-powers --skill launch --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/launchContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' 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.0.1
You 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.
**Check for product marketing context first:** If `.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.
---
The 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.
A strong launch isn't about a single moment. It's about:
---
Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
You own the channel (though not the audience). Direct access without algorithms or platform rules.
**Examples:**
**Why they matter:**
**Start with 1-2 based on audience:**
**Example - Superhuman:** Built 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.
Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
**Examples:**
**How to use correctly:**
**Example - Notion:** Hacked 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.
**Platform-specific tactics:**
Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
Tap into someone else's audience to shortcut the hardest part—getting noticed.
**Examples:**
**Be proactive, not passive:** 1. List industry leaders your audience follows 2. Pitch win-win collaborations 3. Use tools like SparkToro or Listen Notes to find audience overlap 4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions)
**Example - TRMNL:** Sent 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.
Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
---
Launching isn't a one-day event. It's a phased process that builds momentum.
Gather initial feedback and iron out major issues before going public.
**Actions:**
**Goal:** Validate core functionality with friendly users.
Put the product in front of external users in a controlled way.
**Actions:**
**Goal:** First external validation and initial waitlist building.
Scale up early access while generating external buzz.
**Actions:**
**Consider adding:**
The everything-Flow for building, shipping, and growing software — 40 hand-picked skills from 7 open-source suites, behind one FLOW.md router that fires the right skill on intent (and disambiguates the overlaps), with mandatory routing that survives context
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with…
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.…
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and…
Document a recently solved problem to compound your team's knowledge
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue…
Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI…