| name | linear-ticket-routing |
| description | Route a Linear ticket to the correct skill based on its action label (epic, research, prep, bug, execute, review — with or without |
| scopes | ["linear","slack"] |
Linear Ticket Routing
Route a Linear ticket to the correct skill by reading its #-prefixed action labels.
Use this when picking up a ticket from a non-webhook entry point (e.g. Slack, manual prompt). The Linear webhook handler does this routing automatically — this skill is for all other paths.
Steps
- Fetch the ticket using
linear_issue (action: view).
- Check the ticket's labels for action labels. Labels may appear with or without the
# prefix — both #research and research are equivalent.
- If multiple action labels are present, pick the highest priority from the table below.
- Check for the
#verbose modifier (see below).
- Read and follow the corresponding skill.
Routing Table
| Label | Priority | Skill | What it does |
|---|
#epic | 0 (highest) | linear-epic | Orchestrate an epic — break down, sequence, and drive sub-issues to completion. |
#bug | 1 | linear-bug | Investigate bug, identify root cause, fix it, open a PR. |
#research | 2 | linear-research | Deep-dive research, produce a written report. No code changes. |
#prep | 3 | linear-prep | Size, research, enrich context, write implementation prompt. No code changes. |
#execute | 4 | linear-execute | Implement the solution and open a PR. |
#review | 5 (lowest) | linear-review | Review the linked PR for correctness and style. No code changes. |
Modifiers
Modifiers can be combined with any action label.
| Modifier | Effect |
|---|
#verbose | Be over-communicative. Before each phase, explain what you're about to do. Ask clarifying questions on the ticket before proceeding whenever there is any ambiguity. Surface all assumptions and ask for confirmation. Report progress at every step. When in doubt, ask. |
