analysis-skill-routerlisted

# analysis-skill-router ## When to use Use this skill when: * A request may need deep analysis * It is unclear which analysis skill should be used * Multiple analysis skills could plausibly apply * The stack/framework is known but the correct analysis path is unclear * `analysis-autonomous-mode` needs a routing decision Do NOT use when: * The correct specialist skill is already obvious * The task is not an analysis task * The task is normal implementation work without investigation needs ## Procedure ### 1. Identify request scope Classify the request as one of: * full project analysis * architecture review * broad multi-layer debugging * framework-specific deep analysis * narrow root-cause analysis * performance/security specialist analysis * simple local code issue ### 2. Check whether deep analysis is justified Use deep analysis only if at least one is true: * the user explicitly asks for broad analysis * the system is unclear or unknown * the issue spans multiple layers * architecture reconstruction is required * the cause is not local and not obvious If none apply → do NOT route to a broad analysis skill. ### 3. Detect framework or system type Check whether the request clearly targets: * Laravel, Symfony, Zend/Laminas, Node/Express, React, Next.js * unknown / mixed stack ### 4. Route to the correct skill #### Broad / unknown system * full project analysis or unclear stack → `universal-project-analysis` * unknown system, discovery-focused → `project-anal