一键导入
growth-loops
Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs.
用 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 | growth-loops |
| description | Design growth loops (Reforge/Balfour framework). Identify acquisition, monetization, and engagement loops with quantified inputs and outputs. |
| model_tier | opus |
Product is past PMF. User asks: "how do we grow X?", "design growth loops for Y", "channel strategy after PMF"
Saved to products/<name>/launch/growth-loops.md:
## Growth Loops — <product>
### Loop 1: <name> — Acquisition / Engagement / Monetization
**Type:** Viral | Content | Paid | Sales | UGC
**Steps:**
1. <action> → 2. <action> → 3. <action> → 4. <action that reinvests in step 1>
**Inputs needed:**
- <e.g. 100 new users/month from cold outreach>
**Outputs produced:**
- <e.g. 30 referrals/month from happy users>
**Loop multiplier:** <e.g. each user generates 0.3 new users = 0.3x compounding>
**Bottleneck:** <which step has the worst conversion or longest time>
**Investment to test:** <hours/dollars to validate the loop works>
### Loop 2: ...
### Loop interaction
How loops feed each other. E.g. Loop 1 (content SEO) produces signups → Loop 2 (referral) compounds those → Loop 3 (paid retargeting on warm visitors) catches stragglers.
### What we deliberately don't do
1. Paid ads before organic loops are proven
2. <other deferrals>
### Measurement
For each loop:
- Loop completion rate (% users who finish all steps)
- Loop cycle time (how long start → reinvest)
- Loop value (revenue or users generated per cycle)
metrics.md and prd.md.factory/playbooks/scale-stage/growth-loops-reforge.mdfactory/playbooks/scale-stage/100-to-1000-customers.md