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 RAMP profile result. It works one lever — community submission execution — and hands off.

Scope guard: this skill prepares community/directory submissions only. It does not run paid amplification, creator campaigns, media relations, the launch-day runbook, telemetry, or canonical launch state. T-0 observations become authorized idempotent launch proposals through registry-events.py; launch-registry resolves them. Ongoing community presence/warmup belongs to the social discipline.

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.