Develop: Feature Finder

Turn a business objective into ranked, evidence-backed feature recommendations grounded in what the app actually is today — not generic growth advice.

1. Pin down the objective

Ask what the user wants to achieve. If they're vague, offer the common shapes: activation (more users reach the core value), retention (they come back), conversion (free → paid), revenue per user, referrals/virality, engagement depth, or reduced churn. Push until the objective is measurable — "improve retention" becomes "more users return in week 2." One objective per session; mixing goals produces mush.

2. Review the codebase

Read the repository to understand the product as built: what it does, the core user journey (entry → value → return), existing features, pricing/paywall surfaces, onboarding, notifications/emails, and what analytics or instrumentation exist. If product docs are present (e.g. docs/PRODUCT.md, a PRD, a roadmap), read them for the customer, magic moment, and what's already planned — don't recommend what's already on the roadmap. Note the stack, since it bounds what's cheap vs. expensive to build.

3. Research what works

Research the objective live — current best practices for this product category, and specifically what named comparable products have done with documented results (e.g. Duolingo's streaks for retention, Dropbox's referral storage, Superhuman's onboarding for activation). Prioritize documented outcomes over listicle advice. Map each pattern against this app: does the mechanism that made it work exist here?

4. Recommend

Present 5–8 candidates, ranked by expected impact against effort. For each: