Agent skill · wondelai
grow-app
Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says ''users sign up then disappear''. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.
What it needs
About 12k tokens when loaded.
What this skill does
Grow an App Your app has users who sign up and then quietly disappear — cohorts decay, daily actives are flat, the activation funnel leaks where it always has, and nothing looks obviously broken. This journey seals the bucket: it turns first-time users into activated, then habitual, then would-miss-it users across eight interactive phases. The agent asks before every decision and records the outcome in docs/, so the work resumes across sessions instead of restarting. Growth here is an engineering and design problem, not a bigger ad budget. Core Principle Fix the leaky bucket before pouring in acquisition: habit, activation, and retention come before any growth spend. This skill sequences the eight phases, asks every decision question, and records each choice in docs/. The constituent skills carry the method — invoke them rather than improvising their frameworks. Journey Map Phase Skill Question it answers Artifact --- --- --- --- 1 hooked-ux Why do users come back without us paying? Extends docs/PRODUCT.md 2 improve-retention Why don't new users reach the loop? Extends docs/PRODUCT.md 3 continuous-discovery What do our own users actually need? Extends docs/PRODUCT.md + docs/CUSTOMER.md 4 lean-ux Which bet is worth building? Extends docs/EXPERIMENTS.md 5 inspired-product Is the team building the right things? Extends docs/PRODUCT.md 6 lean-analytics Which single number tells the truth? Creates docs/METRICS.md — sets the Rule 8 bar 7 microinteractions Does it feel alive in the hand? Extends docs/DESIGN.md 8 drive-motivation Will engagement last, or curdle? Extends docs/PRODUCT.md Phases 1-2 seal the loop and the funnel; 3-5 steer with evidence; 6 is the instrument panel; 7-8 are the finish and the ethical backstop. Take the lean-analytics baseline (Phase 6) early — before the Phase 1-2 fixes land — so every change is read against a pre-change number, then keep updating it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wondelai/grow-app--7c63c0