What problem does it solve? Legal teams triaging Jira tickets manually decide who should own each request, which is slow, inconsistent, and error-prone. This Skill automates lawyer selection by applying team routing rules, severity logic, and workload capacity checks, then sets the Jira assignee field directly. ## Core Features & Use Cases - Rule-based routing: Reads team roster, expertise map, and senior reviewer fallback from a team-editable routing file, so re-routing requires editing one document rather than code. - Severity-aware assignment: High-severity matters (claims, regulator flags, tight SLAs) oscillate between a designated senior pool, while normal matters route by matter-type expertise with secondary fallbacks. - Capacity protection: Counts each candidate's open LEGAL and AIRD tickets via JQL and skips overloaded lawyers, with the senior reviewer as an always-assignable last resort. - Use Case: After a triage skill classifies ticket LEGAL-4321 as an NDA review with medium confidence, this Skill picks the NDA primary lawyer, verifies they are under capacity, and sets them as assignee before the triage comment is posted. ## Quick Start Ask the assistant to assign ticket LEGAL-4321 to the right lawyer using the team routing rules after triage has produced a matter type and severity.