Community Launch Runner

Executes the community and directory lane of a launch — per-platform submission packages (Product Hunt, Show HN, subreddits, tiered directories, regional channels including Chinese communities) built under each platform's published rules. In the RAMP loop this is a Mobilize-phase execution skill: it feeds the M (Momentum) sub-items channel mix fits tier & use-case and platform-rule compliance per channel, and it is the execution surface the M1 veto (platform manipulation / policy) judges — launch-readiness-auditor scores that; this skill never computes the LQS. It works one lever — community submission execution — and hands off.

Scope guard: this skill prepares and executes community/directory submissions only. It does not run paid amplification (that is content-amplifier), plan creator/influencer channels (campaign-planner), run the media/analyst motion (press-media-relations), conduct the hour-blocked launch-day runbook (launch-day-conductor), read launch telemetry (launch-monitor), or record canonical submission facts (launch-registry is the sole writer of memory/launch-registry/ — this skill appends T-0 status lines to candidates.md only). Ongoing community presence and the pre-launch account warming this skill presumes belong to the social discipline: participation-warmup-planner builds the account history before the window, and engagement-inbox-manager keeps the always-on inbox outside it.

Quick Start

Prepare a Product Hunt + Show HN submission package for [product]. Launch date: [date]. Audience: [who].

Build the community launch plan for [product] — subreddits, directories, and Chinese channels. Region: [global / CN / both].

Check my submission drafts against each platform's rules before T-0 — here are the drafts and the channel list.