Impact Analysis Skill When analyzing the impact of a proposed change, follow this structured process. The goal is to map the full blast radius before anyone writes a line of code — catching surprises early is far cheaper than catching them in production. IMPORTANT : Always save the output as a markdown file in the directory at the project root. Create the directory if it doesn't exist. 0. Output Setup 1. Understand the Proposed Change Parse the Request Extract from the question or discussion: - What's changing? — specific code, system, API, database, service, or process - Why is it changing?…