← ClaudeAtlas

growth-engineeringlisted

Use when designing growth infrastructure including onboarding funnels, referral mechanics, A/B test instrumentation, and re-engagement loops. Covers activation metrics, funnel mapping, and experimentation design. Do not use for pricing or paywall architecture (use monetization-design) or product copy and naming (use messaging-strategy).
dtsong/agentic-council · ★ 0 · DevOps & Infrastructure · score 78
Install: claude install-skill dtsong/agentic-council
# Growth Engineering ## Purpose Design the growth engineering infrastructure for a product feature, including onboarding funnel optimization, referral system mechanics, and A/B test instrumentation. ## Scope Constraints Analyzes product flows, conversion metrics, and experimentation architecture. Does not implement code, modify production systems, or access user data directly. ## Inputs - Product feature being designed - Current onboarding flow (if exists) - Target activation metric ("aha moment") - User acquisition channels - Existing analytics infrastructure ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Activation metric defined - [ ] Step 2: Onboarding funnel mapped - [ ] Step 3: Onboarding flow designed - [ ] Step 4: Referral mechanics designed - [ ] Step 5: A/B test infrastructure instrumented - [ ] Step 6: Re-engagement loops designed ### Step 1: Define the Activation Metric Identify the "aha moment" — the action that correlates with long-term retention: - What specific action indicates the user has gotten value? - How quickly should a new user reach this action? (target: under 60 seconds for simple products, under 5 minutes for complex ones) - What's the current activation rate? What's the target? ### Step 2: Map the Onboarding Funnel Trace the path from first visit to activation: - **Entry point -> Sign up -> First a