analysis-skill-router

# analysis-skill-router A chooser, not a worker. It answers exactly one question — *which skill* — and then gets out of the way. How to actually carry out the work belongs to whichever skill this picks; a chooser that also explains the work reads like its own fallback target, which is the defect this file was cut back from. ## 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. Classify the scope Pick one: full project · architecture review · broad multi-layer debugging · framework-specific deep dive · narrow root cause · performance/security specialist · simple local issue. **Broad scope requires a reason.** At least one must hold, or the answer is a narrow specialist: the user asked for breadth · the system is unknown · the issue spans layers · architecture must be reconstructed · the cause is non-local. ### 2. Detect the framework Laravel · Symfony · Zend/Laminas · Node/Express · React · Next.js · unknown or mixed. ### 3. Read the decision table | Signal | Route to | |---|---| | Full audit, or unclear stack | `universal-project-analy...