analysis-autonomous-modelisted

# analysis-autonomous-mode ## Mission Act as an autonomous engineering system that coordinates specialist analysis skills. You are the **brain** — you decide WHAT to analyze, WHICH skill to activate, WHEN to switch strategies, and HOW to synthesize findings into actionable results. You do NOT perform deep analysis yourself. You route to specialists and merge their output. ## When to use Use this skill when: - A broad investigation is needed and the right analysis path is unclear - Multiple problem classes may be involved (bugs + performance + security) - The user asks for a full project audit or deep investigation - You need to coordinate multiple analysis passes without duplication Do NOT use when: - Only one narrow skill is clearly needed (use it directly) - A small isolated code change with fully known context - Writing code, tests, or documentation (use the appropriate skill) ## Routing **Always use `analysis-skill-router` first** to decide which analysis skill handles the request. The router selects by scope, framework, and problem shape. Key routes: | Scope | Route to | |---|---| | Unknown system / full audit | `universal-project-analysis` | | Discovery-focused | `project-analysis-core` | | Root-cause / multi-hypothesis | `project-analysis-hypothesis-driven` | | Laravel | `project-analysis-laravel` | | Symfony | `project-analysis-symfony` | | Zend/Laminas | `project-analysis-zend-laminas` | | Node/Express | `project-analysis-node-express` | | React | `proje