issue-fetchlisted

# Issue Fetch Fetch full context for a work item before any planning or implementation begins. The tracker is configured once (see below); this skill speaks to whichever one the team uses. ## Trigger Any prompt containing an issue reference, or an explicit request to fetch/work on a story. Reference shapes differ by tracker: | Tracker | Key shape | Example | |---|---|---| | Jira | `[A-Z][A-Z0-9]+-\d+` | `PROJ-1234` | | Linear | `[A-Z]+-\d+` | `ENG-42` | | GitHub Issues | `#\d+` or `owner/repo#\d+` | `#123` | | Azure DevOps | `#?\d+` (work item id) | `#4567` | ## Project configuration Read `.claude/dev-kit.json` at the consuming repo root. The `tracker` block names the active adapter and its settings: ```json { "tracker": { "type": "jira" | "linear" | "github" | "azure", ... } } ``` **If the file does not exist (or has no `tracker` block), run the `dev-kit-setup` skill first** — it detects the tracker, gathers what it needs, persists the file, and returns here. Do not ask the user for values that setup can discover. If the requested key's project/prefix does not match the configured one, confirm with the user before fetching (it may be a cross-project item — allowed, just not silently). ## Adapters — how to fetch Use the adapter matching `tracker.type`. In every case request at minimum: **summary/title, type, status, priority, assignee, reporter, labels, description, acceptance criteria, and all comments** (plus story points and sprint/cycle when the tracker has the