What problem does it solve? Teams often open a Discord, Slack, or forum because it feels like progress, then watch it become a ghost town. This Skill forces the launch decision through five evidence-based readiness gates before any platform is discussed, and produces a defensible launch brief with thresholds and shutdown criteria set in advance. ## Core Features & Use Cases - Readiness gates and verdicts: Scores demand, owner, purpose, venue vacuum, and seed supply, then returns launch, launch-later, or do-not-launch with cheaper alternatives ranked by evidence per standing hour. - Venue class selection: Ranks forge-native discussions, rented public spaces, owned async forums, and owned real-time chat on efficiency, effort, value, and compliance cost, with constraints that delete classes outright. - Seeding and 90-day plan: Designs the founding cohort, seeded posts, opening sequence, rituals, day-90 pass thresholds, and fold-back criteria, delivered as a section-by-section Community Launch Brief. - Use Case: A CTO asks for a Discord because competitors have one. The Skill scores the gates, finds demand and venue-vacuum failing, and recommends participating in the existing ecosystem space instead, with an observable re-decision trigger. ## Quick Start Ask the assistant to evaluate whether your team should launch a developer community and produce a launch brief with venue choice, seeding plan, and go/no-go thresholds.
