Skip to main content
skill CX Codex

growth-loops · phuryn/product-engineering — Claude Code skill: product growth and install

This Claude Code skill evaluates product growth loops. Ask it to compare viral sharing, referrals, collaboration, or user-generated content and map out an implementation plan.

MIT ★ 741 updated 2026-11-14

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/product-engineering
/plugin install product@product-engineering
Open on GitHub

What growth-loops does

The skill assesses five growth loops for a product: viral, usage, collaboration, user-generated content, and referral. It ranks their fit, recommends a primary loop, and lays out implementation steps, metrics, and a 30-60-90 day roadmap. The analysis also estimates a loop coefficient and growth projections.

Pass product context through $ARGUMENTS: describe the product, its main user action, target audience, sharing or collaboration features, current growth channels and metrics, plus constraints or opportunities. The analysis identifies the user action, what it produces, and how it can bring in the next user. A user-generated loop needs enough quality content to keep going.

What it helps with

  • compare growth loops for a product
  • choose a primary user-acquisition mechanism
  • plan loop implementation and measurement
  • identify a likely break point in a growth loop

Example prompts for the agent

  • Assess growth loops for our product using its main user action, audience, and current acquisition channels.
  • Compare viral, referral, and collaboration loops for this product and propose an implementation plan.
  • Create a product growth plan with metrics and a 30-60-90 day roadmap.

How to install growth-loops

1Plugin marketplace

/plugin marketplace add phuryn/product-engineering
/plugin install product@product-engineering

This installs the whole product plugin with all its skills

2Skills CLI (Vercel)

npx skills add phuryn/product-engineering --skill growth-loops -a claude-code

3Manually: put the files in place

~/.claude/skills/growth-loops/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/growth-loops/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about growth-loops

How do I install growth-loops in Claude Code?

Add the marketplace with /plugin marketplace add phuryn/product-engineering, then install the plugin with /plugin install product@product-engineering.

What does growth-loops do?

It ranks five growth loop types for a product and produces an implementation plan with metrics and a 30-60-90 day roadmap.

Which growth loops does growth-loops assess?

It assesses viral, usage, collaboration, user-generated content, and referral loops.

Source text

SKILL.md · MIT
---
name: growth-loops
description: "Designing how a product grows: loops that compound (viral, usage, collaboration, user-generated, referral)."
---

# Growth loops

## Overview

**Identify and design growth loops (flywheels) that compound user acquisition through the product.** Evaluate five proven mechanisms for sustainable traction, reducing reliance on paid acquisition and building product-led growth.

## When to use

Use this analysis for:

- Designing growth mechanisms for a product
- Building sustainable viral or referral traction
- Reducing reliance on paid acquisition
- Analyzing competitor growth strategies
- Optimizing a product for product-led growth

## The 5 growth loop types

### 1. Viral loop

**Shared user-created product content brings new users back to the product.** Users share it on external platforms.

| Aspect | Details |
|---|---|
| Mechanism | Users create content in-product → Share on social/external platforms → New users discover and signup |
| Example | Figma designs shared as links, Loom videos shared in emails |
| Strength | Exponential user acquisition if content is inherently shareable |
| Challenge | Requires highly shareable output and strong incentive to share |

### 2. Usage loop

**Sharing content or value created in-product invites new users or drives re-engagement.**

| Aspect | Details |
|---|---|
| Mechanism | User creates → Shares creation → Others consume → Become engaged users |
| Example | Twitter threads, Medium articles, Notion templates shared publicly |
| Strength | Growth tied directly to product usage and network effects |
| Challenge | Requires content creation friction to be very low |

### 3. Collaboration loop

**Inviting colleagues to co-create expands the user base within organizations.** Users invite them to collaborate within the product.

| Aspect | Details |
|---|---|
| Mechanism | User creates → Invites colleagues for collaboration → Colleagues discover product value |
| Example | Google Docs invitations, Figma team projects, Slack channels |
| Strength | Deep organizational penetration and high retention |
| Challenge | Works best for collaborative/team-based products |

### 4. User-generated loop

**Users discover others' creations, then create and share their own content.** They discover new content or features through those creations.

| Aspect | Details |
|---|---|
| Mechanism | User discovers content → Creates similar content → Shares creation → Others discover |
| Example | TikTok, Pinterest, YouTube trends driving creator participation |
| Strength | Creates content flywheel and network effects |
| Challenge | Requires critical mass of quality content to sustain |

### 5. Referral loop

**Users invite potential users for rewards, incentives or social recognition.**

| Aspect | Details |
|---|---|
| Mechanism | User refers → Referred user joins → Referrer gets reward → Shares more referrals |
| Example | Dropbox referral bonus, Uber rider referrals, PayPal signup bonuses |
| Strength | Directly incentivizes acquisition; easy to measure ROI |
| Challenge | Requires valuable incentive without eroding unit economics |

## How it works

### Step 1: Define product value

**Clarify the core value users experience.** Identify:

- The primary action users take in your product
- Value created per user action
- Network effects present (if any)
- Friction points in the experience

### Step 2: Evaluate loop fit

**Assess which growth loops align with your product.** Consider:

- Product type (collaborative, content-based, utility, etc.)
- Target user behavior and sharing habits
- Network effects already present
- Existing user base and engagement

### Step 3: Design loop mechanics

**Design the specific mechanics of the loop.** Include:

- The trigger that initiates sharing or invitations
- Incentive for participation (intrinsic or extrinsic)
- Ease of the sharing mechanism
- Conversion rate from invite to activation
- Frequency of loop repetition per user

### Step 4: Calculate loop coefficient

**Estimate growth velocity and the loop coefficient.** Calculate:

- Invites/shares per user per cycle
- Conversion rate of invites to new users
- Net new users per cycle
- Time per cycle iteration

### Step 5: Build the loop

**Implement the highest-leverage loop first.** Start with the most natural loop for your product. Optimize messaging and friction, measure loop metrics and conversion rates, and compound results over time.

## Input format

**Pass the product and growth context through $ARGUMENTS.** Include:

- Product description and primary user action
- Target user demographics and behavior
- Existing sharing/collaboration features
- Current growth channels and metrics
- Constraints or opportunities

## Output

**Produce a ranked growth-loop analysis and implementation plan.** Include:

- Ranked evaluation of all 5 loop types for your product
- Recommended primary growth loop with implementation plan
- Secondary loops to layer over time
- Key metrics and measurement framework
- 30-60-90 day implementation roadmap
- Potential loop coefficient and growth projections

## Framework

Based on growth loops research by Ognjen Bošković. The focus is compounding user acquisition through built-in, product-native sharing and collaboration mechanisms.

## Tips

- **Start with one loop and master it before adding complexity.**
- **Viral loops compound fastest but take time to build.**
- **Collaboration loops create the strongest retention and LTV.**
- **Measure loop health weekly during the optimization phase.**
- **Combine loops for multiplicative effect once operating at scale.**

## How you can tell it worked

Each loop names who acts, what their action produces and how that brings the next user. The step most likely to break is marked as the one to test.

© Paweł Huryn · MIT · phuryn/product-engineering

Similar skills

All skills for Marketing and content →

growth-loops by other authors comes first.

growth-loops phuryn The growth-loops skill helps identify and design growth loops for your product. Evaluates five loop types, from viral to referral. CX Codex +1 3,100installs growth-loops AIDevGTM A skill for Claude Code, Codex, Cursor, Copilot, Gemini CLI, and OpenCode that moves a dev tool from manual outreach to growth loops. It diagnoses why product usage brings zero new users and picks one loop instead of piling on channels. CX Codex +1 ★ 344repo stars growth-model RefoundAI growth-model guides you to replace linear funnels with compounding growth loops. Useful when auditing acquisition engines, retention loops, and spreadsheet models. CX Codex +1 468installs growth-strategy manojbajaj95 growth-strategy designs compounding growth loops, evaluates network effects, and models unit economics. It shifts product teams from linear funnels to product-led loops. CX Codex +1 342installs growth-marketer borghei growth-marketer is a Claude Code skill for planning experiments, mapping the AARRR funnel, and comparing acquisition channels. It helps choose a growth metric or assess a hypothesis. CX Codex +1 433installs growth-hacking vivy-yi growth-hacking — a skill for systematic testing and optimization of Xiaohongshu account growth. Identifies growth bottlenecks, engineers viral mechanics, and accelerates follower acquisition 10–100x through experimentation, not effort. CX Codex +1 215installs list-growth-designer aaron-he-zhu list-growth-designer designs an email list acquisition plan, lead magnet concepts, and a double opt-in capture specification tailored to regional jurisdiction rules. CX Codex +1 1,100installs referral-growth vivy-yi referral-growth provides growth playbooks for Xiaohongshu through share triggers, viral challenges, and follower referral programs. CX Codex +1 164installs

From the same set51

The whole set →
handover This Claude Code skill writes a handover for the next agent session. It checks the project against the files on disk and records verified facts, unfinished work, and a concrete next step. CX Codex +1 ★ 741repo stars intended-vs-implemented The intended-vs-implemented Claude Code skill checks whether code follows documented requirements and spots gaps in access control and data boundaries. It audits AI-built features for security and correctness issues. CX Codex +1 ★ 741repo stars value-proposition This Claude Code skill shapes a value proposition with a six-part JTBD structure. It covers a customer segment, its task, the current approach and alternatives. CX Codex +1 ★ 741repo stars competitor-analysis competitor-analysis — a Claude Code skill for mapping market rivals and product substitutes. It analyzes five direct competitors, flags functional gaps, and highlights strategic differentiation points. CX Codex +1 ★ 741repo stars beachhead-segment The beachhead-segment Claude Code skill scores candidate customer segments and selects a first market to pursue. It weighs customer pain, willingness to pay, winnable share and referral potential. CX Codex +1 ★ 741repo stars retro The retro Claude Code skill reviews session friction and turns verified causes into changes to the agent setup. Start it by name at the end of a session. CX Codex +1 ★ 741repo stars value-curve This Claude Code skill maps a product’s value curve for one customer segment. It compares key needs, competing offers and relative price. CX Codex +1 ★ 741repo stars document-app The document-app Claude Code skill documents an app from its code or checks whether existing docs match the implementation. It runs on requests to document an app or verify its system documentation. CX Codex +1 ★ 741repo stars

Project sponsors

Companies that keep this analytics open