coupling-reviewlisted

# Coupling Review When this skill is activated, analyze the coupling structure of a specified module, feature, or the entire codebase and produce a `docs/reviews/COUPLING_REVIEW.md` report. ## Clarifying Questions Before starting the review, ask the engineer the following questions. Skip any already clearly answered in the conversation. **Wait for the answers before proceeding.** 1. What is the scope — a specific module or feature, or the full codebase? 2. What is the goal of this review? (e.g. before a refactor, identifying change-propagation risk, understanding dependencies) 3. Which areas of the codebase change most frequently — where does coupling hurt the most today? 4. Are there specific cross-module or cross-context dependencies you already suspect are problematic? ## Steps 1. Use the answers above to set scope and focus; fall back to full codebase only if scope was not specified 2. Read the relevant source files and map all dependencies between components 3. Classify each coupling by type and assess whether it is intentional or accidental 4. Identify coupling smells: hidden dependencies, inappropriate intimacy, unstable dependencies, circular references 5. Propose concrete refactoring steps for each problematic coupling ## Output Write a file called `docs/reviews/COUPLING_REVIEW.md` (create the `docs/reviews/` folder if it does not exist) with the following sections: ### 1. Scope What was analyzed (files, modules, feature boundaries). ### 2. Dependency Map A