القائمة
Build a community around the product — Discord/Slack/forum, waitlist nurture, early-user comms. Choose the right venue, don't default to Discord.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
| name | community-builder |
| description | Build a community around the product — Discord/Slack/forum, waitlist nurture, early-user comms. Choose the right venue, don't default to Discord. |
| model_tier | sonnet |
User asks: "should I start a Discord?", "how do I build a community for X?", "waitlist nurture for Y", "engage my early users"
Saved to products/<name>/launch/community.md:
## Community Strategy — <product>
### Should we have a community? (be honest)
- ✅ Yes if: users want peer-to-peer help, learn-from-each-other use cases, vertical with strong network effects
- ❌ No if: users just want the tool to work, B2B with sensitive use cases, < 100 active users
### If yes — pick the venue
| Venue | Best for | Cost | Maintenance |
|---|---|---|---|
| Discord | dev tools, creators, gaming, consumer | free | high (mods, abuse) |
| Slack Connect | B2B, customer success | free | medium |
| Circle / Skool | structured cohorts, paid | $99+/mo | medium |
| Newsletter + comments | broad audience, async | free | low |
| GitHub Discussions | OSS / dev tools | free | low |
| Existing subreddit | tap into existing community | free | very low |
Recommendation: <pick one>. Why: <reasoning>.
### Waitlist nurture (pre-launch)
- Welcome email (T+0): set expectation, ask 1 question ("what made you sign up?")
- Update email (T+14): show progress, share an asset
- Pre-launch email (T-2): reminder + sneak peek
- Launch email (T-0): go-live + how to start
### Early-user comms (post-launch, first 100)
- Personal welcome from founder (every single new signup, for the first 100)
- Day 3: "how's it going?" check-in if not activated
- Day 7: Sean Ellis survey
- Day 30: NPS + ask for testimonial if positive
### Content cadence (in community)
- Weekly: founder update (what shipped, what's next, ask for input on one thing)
- Daily: light engagement — surface questions, celebrate wins
- Don't: post every blog promo. Communities die when they feel like a marketing channel.
### Moderation
- Code of conduct: short, plain English, posted
- Mods: founder is mod #1 for the first 6 months; add 1–2 community mods at ~500 members
- Bans: documented; no surprise bans
factory/playbooks/launch-stage/first-100-customers.md