fetch-ticket

# Ticket Fetcher **Fetch only** — no analysis, requirements, or planning. Output is a self-contained `.TICKET.md`. ## Source & access Identify the tracker from the input (URL host, or id shape) and fetch through the matching MCP server — e.g. **Azure DevOps MCP** for ADO work items, **Atlassian MCP** for Jira issues, **GitHub MCP / `gh`** for GitHub issues. Use whichever equivalent tools are connected; tool name prefixes vary by config. Resolve once any handle the MCP needs (e.g. Atlassian `cloudId`, ADO project) and reuse it. If the input is ambiguous, ask the user — don't guess. If no matching MCP is connected: a public ticket may be scraped from its URL as a fallback (you may still suggest installing the matching MCP when it would do the job better); a private one can't — the URL returns a login page, not the ticket — so stop and tell the user to install and authenticate the matching MCP server, then re-run. ## Your task 1. **Resolve the input.** Accept a full ticket URL or a bare id/key; extract the identifier. If the tracker uses a key prefix (e.g. `XX-1234`), keep it; otherwise use the bare number. If the input is unrecognizable, ask. 2. **Fetch the ticket.** Get the work item/issue with its full field set, comments inline, and related links/relations expanded. Capture **everything** the ticket carries — don't pre-filter to a fixed set of fields. Convert whatever rich-text form you get (HTML, ADF, …) to clean Markdown. 3. **Pick a slug.** Short kebab-ca...