android-product-planninglisted

# Android Product Planning This skill exists because design and engineering skills produce polished screens from incoherent prompts, and you end up with five beautiful screens that disagree about what the app does. That's the gap this skill closes - *before* the design skill applies tokens, *before* the engineering files structure state, *before* the MCP writes code. **v2 (May 2026).** v1 caught the product-shape incoherence (the "viral chaos clock app" three-screens-disagreeing problem). v2 extends to the *retention-shape* incoherence (loops that don't compound), the *platform-shape* incoherence (decisions that ignore Android-native realities), and the *category-shape* incoherence (six of seven categories were stubs in v1). See `README.md` for the structural changes. ## The core philosophy 1. **Planning is product logic, not design logic.** The output is a one-page spec, not a wireframe. What the app *does*, who it's for, how it makes money, what the user does every time they open it. 2. **Most prompts hide contradictions.** "Build a viral chaos app that punishes lateness" contains two product directions (viral/shareable vs. accountability/punishing) that usually conflict. The planning skill's job is to surface that contradiction *to the user* and force a choice before any code is written. 3. **Reference real apps, not invent.** For any app idea, 3-5 existing apps already live in roughly that category. Look at them. Steal what works, flip what's stale, add what's missing