Product Launch Strategy & Multi-Channel Kit

What it does

/launch is a Cursor slash command. Type it in chat to run a saved workflow: Product Launch Strategy & Multi-Channel Kit.

Coordinates public product launches: creates Product Hunt submissions, Show HN posts, viral X threads, and hour-by-hour launch day timelines.

Product Hunt, Show HN, X/Twitter, and launch day promotion execution plans. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /launch for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /launch exists so the pipeline, all 5 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to Product Launch Coordinator (launch-coordinator), Direct Response Copywriter (copywriter), and Social & LinkedIn Strategist (social-media-strategist). Required skills: Product-Led Growth (PLG) & Growth Loops; Eugene Schwartz 5 Stages of Customer Awareness; LinkedIn Thought Leadership & Founder Branding.

When to use it

• Use when preparing to launch your product publicly to maximize day-one traffic and signups.
• Use /launch when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /launch as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. launch-coordinator defines launch positioning and day-one timeline
2. copywriter drafts Product Hunt tagline, description, and maker first comment
3. reddit-strategist crafts authentic Show HN submission text
4. social-media-strategist writes 8-part viral X/Twitter launch thread
5. Auto-saves complete launch kit to docs/marketing/launch/

Example usage

Type this in Cursor chat: /launch Create complete Product Hunt, Show HN, and X launch strategy for developer tool

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/launch/product-hunt.md
• Expected artifact: docs/marketing/launch/show-hn.md
• Expected artifact: docs/marketing/launch/x-thread.md

Best practices

• Keep the prompt specific. /launch Create complete Product Hunt, Show HN, and X launch strategy for developer tool is the shape: object, constraint, and outcome.
• Let the listed agents work in order: launch-coordinator → copywriter → social-media-strategist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /launch with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Product-Led Growth (PLG) & Growth Loops skill that the command depends on.