Product Launch Coordinator

What it does

Product Launch Coordinator is a Cursor agent playbook named launch-coordinator. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The launch-coordinator agent coordinates high-impact public product launches. It crafts compelling Show HN pitches, Product Hunt tagline/first-comment sequences, viral X announcement threads, and day-one launch checklists.

Manages Product Hunt, Hacker News, X/Twitter, and launch day timelines. Product launch coordinator for Cursor that builds launch schedules, Product Hunt submissions, Show HN posts, and social announcement kits.

Why it exists

A pile of agent files is not a team. launch-coordinator exists so one job, product launch coordinator, has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: launch-coordinator; Eugene Schwartz 5 Stages of Customer Awareness; LinkedIn Thought Leadership & Founder Branding. Commands that adopt this role: /launch: Product Launch Strategy & Multi-Channel Kit; /linkedin-post: LinkedIn Thought Leadership & Growth Post; /blog-post: SEO Blog Post & Technical Tutorial Generator.

When to use it

• Launching a new SaaS product on Product Hunt, Hacker News, and X
• Coordinating multi-channel promotional campaigns
• Maximizing day-one traffic and early customer signups

When not to use it

• Do not ask launch-coordinator to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/launch-coordinator is on disk.
2. Run /launch: Product Launch Strategy & Multi-Channel Kit, or start a chat and tell Cursor to adopt the launch-coordinator role.
3. The agent should read: launch-coordinator; Eugene Schwartz 5 Stages of Customer Awareness; LinkedIn Thought Leadership & Founder Branding.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are launch-coordinator. Launching a new SaaS product on Product Hunt, Hacker News, and X. Read launch-coordinator before you edit."

Or let the pipeline invoke it: /launch: Product Launch Strategy & Multi-Channel Kit.

Capabilities you should actually see: Product Hunt submission assets (tagline, description, maker comment)

Example output

• launch-coordinator should leave files or a written verdict, not a vibe check. Product Hunt submission assets (tagline, description, maker comment) Show HN post drafts adhering to strict community guidelines
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Product Hunt submission assets (tagline, description, maker comment)
• Show HN post drafts adhering to strict community guidelines
• X/Twitter viral launch threads and social announcement packs
• Hour-by-hour launch day execution timeline and community outreach
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using launch-coordinator as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.