launch-loop-strategy

name	launch-loop-strategy
description	Use when planning a practical launch loop for a feature, product update, template, prompt, skill, integration, beta, or release with a known launch date, especially when the user needs channels, content angles, a posting schedule, community distribution, replies, DMs, and follow-up remixes.

Launch Loop Strategy

Turn one feature launch into a week of useful market contact. The user should be able to say:

I'm launching <feature> on <date>. Help me build the launch loop.

Return a practical plan: what to post, where to post it, what assets to make, what to say, how to reply, and what to remix after the first signal comes in.

Use this skill with:

• launch-strategy for broader GTM sequencing, launch checklists, beta launches, and waitlists.
• distribution-plan for channel selection, communities, partners, newsletters, PR, and founder-led distribution.
• content-strategy for pillars, narratives, recurring formats, and proof/story inventory.
• creative-brief for ad, social, image, video, UGC, and creator asset briefs.
• x-article-writer when the loop needs a long X/Twitter article, founder essay, or launch teardown.

Core Loop

Do not launch once. Launch the loop:

Demo -> Post -> Share -> Reply -> Repost

1. Demo: show or explain one launchable unit: feature, workflow, skill, template, proof point, or lesson.
2. Post: publish the strongest anchor asset: demo, carousel, thread, article, short video, or teardown.
3. Share: distribute native versions across the channels where this category fits.
4. Reply: answer comments, DMs, objections, and confusion; collect the market's language.
5. Repost: turn the winning angle, question, objection, or proof into the next asset.

The operating principle:

Launch once and you get a spike.
Launch every week and you get distribution.

Intake

When details are missing, ask at most three useful questions. Otherwise infer and state assumptions.

Minimum inputs:

• Feature: what is shipping.
• Date: exact launch date or rough window.
• Audience: who should care.
• Promise: what pain changes after this exists.
• Proof: screenshot, demo clip, metric, quote, customer result, build note, before/after, or waitlist.
• Channels: where the user can realistically post.
• CTA: try it, join waitlist, comment keyword, DM, install, book call, read docs, or share.

Default assumptions:

• Use a 7-day loop: 2 days before launch, launch day, 4 days after.
• Use one anchor asset, one short-form discovery asset, one community-native post per relevant channel, and one remix from early feedback.
• If the user has little or no audience, prioritize short-form discovery, X/community posts, and direct community distribution over Stories.

Build The Angle

Name the launchable unit in one sentence, then choose the strongest angle:

• Pain killer: Stop doing <old painful workflow>.
• New mechanism: The better way is <new workflow>.
• Proof: We tested/built/shipped <specific proof>.
• Comparison: Before <feature> vs after <feature>.
• Founder lesson: We learned <truth> building this.
• Category shift: <old category habit> is becoming <new behavior>.

Write the audience promise as:

This helps <person> do <outcome> without <pain>.

Major Feature System

Use this for major features, not tiny fixes. Package the same feature as a week of market contact from different angles:

1. Product demo: what changed and why it matters.
2. Best use case clip: the clearest "I need this" moment.
3. Problem angle: what painful old behavior this replaces.
4. Workflow angle: the new step-by-step process.
5. Proof angle: metric, customer quote, screenshot, build note, or before/after.
6. Founder POV: why the team built it this way.
7. Community-native version: rewritten for the specific platform.

The feature should appear from multiple angles for a full week without copy-pasting the same announcement everywhere.

7-Day Template

Use this when the user gives a launch date:

T-2: Tease the problem
T-1: Show the old workflow / pain
Launch day: Demo the feature + anchor post
T+1: Post the best use case as a short clip/Reel
T+2: Share community-native versions
T+3: Answer objections / publish FAQ
T+4: Repost winner + recap what people missed

For each day, specify:

• Post format.
• Hook.
• Channel.
• Asset needed.
• CTA.
• Signal to watch.

If launch is imminent, compress to:

Launch day: anchor + demo
Next day: short clip from the demo
Day 3: community post + objection follow-up

Platform Fit

Choose only platforms where the category fits.

• Product Hunt: polished product/update story, launch page, screenshots, maker comments.
• Hacker News / Show HN: technical clarity, direct demo, no marketing fluff.
• Devhunt: developer tool launch, practical workflow, build details.
• BetaList: early product, beta/waitlist positioning.
• Peerlist: builder/founder credibility, product craft, career/professional utility.
• Indie Hackers: build-in-public, revenue/users, founder lesson, tactical breakdown.
• Reddit: subreddit-specific usefulness, low-promo framing, real discussion.
• X: sharp POV, demo clip, thread, founder narrative, quote-post remixing.
• LinkedIn: professional pain, team/business outcome, clear lesson.

Rewrite the intro for each community's norms. Do not dump the same caption everywhere.

Carousel To Short Video

When turning a carousel or deck into a short video, do not animate every slide. Make a trailer.

Use 3-4 frames:

1. Problem frame: names the pain or mistake.
2. Mechanism frame: reveals the new model.
3. Steps/proof frame: shows the process or result.
4. CTA frame: tells viewers what to do next.

Structure:

0-3s: Problem
3-6s: Better mechanism
6-12s: Steps or proof
12-18s: CTA

Use screenshots, screen recordings, product demo clips, captions, cursor movement, and subtle zoom/pan. It should feel like a preview of the full anchor asset, not a duplicate upload.

CTA Rules

Use a comment/DM CTA only when the promised asset exists and the team can deliver it reliably.

Good CTAs:

• Comment LAUNCH and I will send you the checklist.
• Save this before your next feature launch.
• Send this to the founder who only launches once.
• DM me LAUNCH if you want the template.

Avoid:

• Inventing a downloadable asset that does not exist.
• Vague endings like thoughts?
• Asking for comments when the post gives no natural reason to discuss.
• Dropping links in captions as if they are clickable.

First-Hour Routine

Before posting:

• Comment thoughtfully on 5-10 relevant creator/community posts.
• Prepare 3 reply prompts for likely comments.
• Know exactly how to deliver the promised asset if using a keyword CTA.

After posting:

• Reply to every real comment with a specific answer.
• Ask one narrow follow-up question when useful.
• DM the asset only to people who asked for it.
• Save good questions as follow-up post hooks.

Output Contract

Return:

1. Launchable unit: what exactly is being launched.
2. Audience promise: who it helps and what pain it removes.
3. Launch angle: the single strongest narrative for the week.
4. Dated schedule: T-2 through T+4, or compressed if launch is imminent.
5. Asset list: screenshots, demo clips, carousel, short video, community posts, replies.
6. Channel plan: what to post where and how to adapt the intro.
7. First-hour plan: comments, replies, DMs, and follow-up prompts.
8. Remix plan: 3 follow-up angles from expected comments or objections.