What problem does it solve? When facing a bug fix, feature change, new module, or system refactor, teams often either over-engineer simple fixes or under-plan risky changes. This Skill triages every change request into an L0-L3 severity level and routes it to the smallest sufficient workflow, preventing skipped impact analysis on APIs, data, security, and cross-end concerns. ## Core Features & Use Cases - Change Triage: Evaluates public contracts, data impact, cross-end effects, security, module count, compatibility, and rollback risk using a structured checklist. - Level-Based Routing: Maps L0-L3 levels to concrete execution paths, loading only the skills needed for that level (debugging, impact analysis, API contracts, DB migration, security audit, CI/CD). - Escalation Conditions: Outputs explicit upgrade triggers so a change that grows in scope must move to a higher-level process. - Use Case: A developer asked to "just add a field to an API" runs the triage, discovers the change touches a public contract and database schema, and gets routed to an L2 path with API contract and test review instead of a quick edit. ## Quick Start Ask the AI to triage your change request, for example: "Route this change: add a new status field to the order API and update the frontend list page."