outline-understanding-user-request

To clarify ambiguous user requests, you can analyze relevant code flow to identify affected areas and formulate targeted questions about scope and integration points. This approach grounds your clarifying questions in actual code findings.

Gathering requirements for complex code changes is best achieved by mapping data flow across affected files to pinpoint integration points. This allows you to ask precise questions about scope and requirements before implementation begins.

You can scope software features efficiently by analyzing fewer than five relevant files to map data flow and identify affected systems. This targeted code analysis prevents context drain while still uncovering necessary integration points.

You need targeted code analysis for scope definition when a user's request is ambiguous or initial understanding is insufficient after reviewing the code. It helps identify affected systems and precise integration points before implementation.

This code analysis approach works for identifying integration points by focusing your review on fewer than five files. It maps data flow efficiently to pinpoint affected systems within large architectures without draining context.

Analyzing code flow helps formulate better clarifying questions by grounding your inquiries in actual data paths and affected systems. This prevents wasted implementation effort by ensuring questions about scope and requirements are highly targeted.