yeachan-heo-analyze

<Use_When>

• User says "analyze", "investigate", "debug", "why does", or "what's causing"
• User needs to understand a system's architecture or behavior before making changes
• User wants root cause analysis of a bug or performance issue
• User needs dependency analysis or impact assessment for a proposed change
• A complex question requires reading multiple files and reasoning across them </Use_When>

<Do_Not_Use_When>

• User wants code changes made -- use executor agents or ralph instead
• User wants a full plan with acceptance criteria -- use plan skill instead
• User wants a quick file lookup or symbol search -- use explore agent instead
• User asks a simple factual question that can be answered from one file -- just read and answer directly </Do_Not_Use_When>