planning-android-implementation

Start by classifying the change type, then explore the codebase for pattern anchor files and integration points such as Hilt modules and navigation graphs. Next, design the architecture, build a file inventory with risk levels, and break the work into independently testable phases.

A solid plan includes a change classification, pattern anchors from existing code, an architecture diagram of Screen, ViewModel, Repository, and data layers, a file inventory with risk levels, sequential implementation phases, and a risk assessment with verification steps.

Order phases as Foundation, SDK/Data, Network, then UI, keeping each phase independently testable and committable. Write tests within the same phase as the code they verify, and split any phase containing more than five tasks.

Refine requirements first whenever the specification is vague or incomplete, since planning depends on a clear set of requirements. A dedicated requirements-refinement step should resolve ambiguities before architecture design and file inventory work begins.

Search for navigation graph registrations, Hilt dependency injection modules, repository and data source interfaces, Retrofit service definitions, feature flags, and shared test fixtures. Use two to three existing files as pattern anchors that demonstrate the conventions to follow.