You are tasked with applying structured prompting to perform impact analysis on recent code changes.

The most effective way to improve an LLM's performance on complex tasks likeimpact analysisis to provide a detailed, multi-stepInstructionorChain-of-Thoughtstructure. Option D is the best improvement because it breaks the "impact analysis" task into logical sub-tasks: mapping changes to modules, identifying related test cases, and prioritizing them based on risk and complexity. This structured approach guides the LLM through the "reasoning" steps a human expert would take, significantly reducing the likelihood of a superficial or incorrect analysis. While specifying a specialized role (Option B) or adding technical references (Option A) can help set the tone, they do not provide the model with the logical framework required to execute the task accurately. By explicitly defining theprocessthe LLM should follow, the tester ensures that the model evaluates the "depth" of the change rather than just listing files. This results in a more robust and actionable regression test suite, which is the primary goal of impact analysis in a modern software development lifecycle.