issue-feature-breakdownlisted

# Feature Breakdown Read-only analysis of a Jira feature ticket. Gathers context, consults the clarity-council, resolves ambiguities with the user, and produces an actionable breakdown. **All operations are read-only. Never create, update, or transition Jira tickets.** ## Input A Jira ticket key (e.g. `PROJ-123`). Extract from the user's message using pattern `[A-Z][A-Z0-9]+-\d+`. ## Workflow ### Phase 1 — Gather Context 1. Fetch the root ticket via `jira_get_issue` — capture summary, description, acceptance criteria, status, priority, story points, fix version, and sprint. 2. Fetch comments via `jira_get_comments`. 3. Walk **all linked tickets** (issue links from the root ticket's `issuelinks` field): - For each link: fetch via `jira_get_issue`, note the link type (blocks / is blocked by / relates to / etc.). - If the root ticket belongs to an **epic/feature**: fetch sibling stories via `jira_get_epic_issues`. 4. Check for **Confluence context**: - Fetch remote links via `jira_get_remote_links` — read any linked Confluence pages via `confluence_get_page`. - Search Confluence via `confluence_search` with CQL: `text ~ "TICKET-KEY"` to find pages that reference this ticket. 5. Compile a **Context Summary** and present it to the user. Include: - Root ticket details - Linked ticket summaries (with link types) - Confluence page titles and key excerpts - Any acceptance criteria found **Gate:** Ask the user if any additional tickets or documents shoul