Mobile App Planner

Turn a vague or one-line request into a stated goal, an inferred goal, and the assumptions it is quietly making, with a verdict on whether it is specific enough to plan from.

Surface the questions that must be answered before work can be scoped, each with the decision it unblocks and what changes depending on the answer, split into blocking and non-blocking.

Map which parts of a mobile system a feature touches — client, backend, admin surface, shared types, integrations — separating what was stated from what was inferred, and naming every API contract change.

Draw the scope boundary for an iteration as three lists — in scope, deliberately deferred, and rejected outright with reasons — plus the item most likely to become scope creep.

Rank work by reversibility rather than effort, treating anything a shipped mobile build depends on as higher risk, and name plainly what cannot be undone.

Assemble the full plan document — goal, scope, success criteria, surface touchpoints, risks, open questions and sequence — writing any section whose material is missing as an honest gap rather than a plausible guess.