ticket-contextlisted

## When to invoke Auto-loads when the caller references: - **Jira key**: `[A-Z][A-Z0-9]+-\d+` — e.g. `PROJ-123`. A bare key routes to Jira by default; see the Linear adapter's Trigger field for the availability tiebreak that reroutes it when only a Linear MCP tool is reachable. - **Atlassian Jira URL**: `*.atlassian.net/browse/<KEY>`. - **Confluence URL**: `*.atlassian.net/wiki/spaces/...` or `*.atlassian.net/wiki/pages/...`. - **Linear URL**: `linear.app/<workspace>/issue/<TEAM-N>` — routes here unconditionally. - **GitHub issue/PR URL**: `github.com/<owner>/<repo>/(issues|pull)/\d+`. - **GitHub short ref**: `#\d+` with current-repo context. If no reference is present, exit cleanly. ## Adapters ### Jira issue - **Trigger:** Jira key (`[A-Z][A-Z0-9]+-\d+`) or Atlassian Jira URL (`*.atlassian.net/browse/<KEY>`). A bare key routes here unless the Linear adapter's availability tiebreak applies. - **Fetch:** First fetch in session: call `mcp__atlassian__getAccessibleAtlassianResources` for `cloudId` (cache for session). Then `mcp__atlassian__getJiraIssue` with the key. - **Extract → block fields:** summary, issuetype, status, priority, description → Title/Type-Status/Summary; labels, components, acceptance-criteria (check description body if no dedicated field) → Acceptance criteria; linked issues via `mcp__atlassian__getJiraIssueRemoteIssueLinks` → Linked references; last 5 comments → Recent activity. - **Degrade:** If Atlassian MCP unavailable, try `mcp__atlassian__fet