<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>

<Why_This_Exists> Deep investigation requires a different approach than quick lookups or code changes. Analysis tasks need broad context gathering, cross-file reasoning, and structured findings. Routing these to the architect agent or Codex ensures the right level of depth without the overhead of a full planning or execution workflow. </Why_This_Exists>

<Execution_Policy>

• Route analysis to the architect Claude agent for thorough investigation

• Always gather context files before spawning the architect agent for grounded reasoning

• Return structured findings, not just raw observations </Execution_Policy>

<Tool_Usage>

• Use Task(subagent_type="oh-my-claudecode:architect", model="opus", ...) as the primary analysis route

• For broad analysis, use explore agent first to identify relevant files before routing to architect </Tool_Usage>

<Escalation_And_Stop_Conditions>

• If analysis reveals the issue requires code changes, report findings and recommend using ralph or executor for the fix

• If the analysis scope is too broad ("analyze everything"), ask the user to narrow the focus

• If Codex is unavailable and the architect agent also fails, report what context was gathered and suggest manual investigation paths </Escalation_And_Stop_Conditions>

<Final_Checklist>

• Analysis addresses the specific question or investigation target

• Findings reference specific files and line numbers where applicable

• Root causes are identified (not just symptoms) for bug investigations

• Actionable recommendations are provided

• Analysis distinguishes between confirmed facts and hypotheses </Final_Checklist>

Task: {{ARGUMENTS}}