grow-app

What it does

Guides a team through an eight-phase retention-focused growth journey for an app, asking questions at each decision point and recording outcomes in docs/ for continuity across sessions. It sequences phases from Hooked-UX to Drive-Motivation to fix activation and retention before acquisition, and ties each phase to specific artifacts in the docs/ folder.

How it works

• It starts by reading existing plan and artifacts in docs/ and resumes a tracker state if present; otherwise it creates a GROW-APP-PLAN.md and populates phase statuses.
• It invokes a phase by its slug (e.g., hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation) with explicit instructions to elicit decisions, capture outcomes, and extend the relevant docs files.
• It asks concrete questions under Decide with the user, records decisions in the tracker, and presents draft artifact content for sign-off before writing into docs/ files.
• If a phase’s dedicated skill is unavailable, it proposes a fallback using a global install command: npx skills add wondelai/skills/<slug> --global; if declined, it runs the phase from its Brief as a minimum viable method.
• It enforces artifact discipline by creating or extending uppercase docs/ files with checkboxes or table rows, preserving existing content.
• It emphasizes retention before acquisition and uses a structured intake to set a baseline and update a single metric ( lean-analytics phase) and subsequent artifacts.

When to use it

Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or when users sign up and disappear. It should not be used to fix broken UX or performance that engagement cannot salvage—run improve-app first; if there is no app yet, use create-app.

What it can touch

• Invokes phase skills by slug (e.g., hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation).
• Creates and extends docs/ files (e.g., docs/GROW-APP-PLAN.md, docs/PRODUCT.md, docs/METRICS.md, docs/EXPERIMENTS.md, docs/DESIGN.md, docs/CUSTOMER.md, docs/EXPERIMENTS.md, docs/OPPORTUNITY SOLUTION TREE NOTES and others as specified by phase).
• Records decisions in the tracker and updates phase statuses and next actions.

Caveats

• The approach relies on explicit user confirmation at each phase entry and sign-off before writing artifacts.
• The backbone is eight phases; it explicitly instructs not to skip gating phases except where allowed (GATE deferment). It requires the user to confirm the plan before proceeding.
• It requires access to a docs/ folder with specific uppercase files and a tracker mechanism to persist state across sessions.