What problem does it solve? When reviewing or modifying code, changing module A often requires changing module B, but these cross-file couplings are only discoverable by reading the entire codebase. This Skill makes such hidden dependencies explicit and searchable, so you know what must change together before you edit. ## Core Features & Use Cases - Coupling Identification: Detects contract coupling (shared DTOs, interface signatures, message formats, shared table schemas) and business coupling (rule dependencies, call ordering, state consistency) across modules. - Direction & Strength Judgment: Evaluates each relation along two orthogonal lines—contract/structure and semantics/behavior—producing triples of source, target, direction, and strength (must-change / should-change / optional). - Persistent Memory Integration: Writes confirmed relations into ki-search via the ki-memory-write skill, grouped by functional module, and verifies writes with ki_query_group. - Use Case: After expert-team creates a module expert asset, automatically record that module's strong couplings so later code reviews can query "if I change A, what else must change". ## Quick Start Ask the AI to record the strong coupling relationships for a specified module, for example: "Record the strong relations between the order module and its dependencies."
