issue-estimate-splisted

# Estimate Estimate story points for a Jira ticket via context gathering and a scrum-poker council session. This is a **read-only** operation. Never update the ticket. ## Input - `ticket_key` (required) — e.g. `ABC-12345` ## Workflow ```text Estimate Progress: - [ ] Step 1: Gather ticket context from Jira - [ ] Step 2: Gather related context (feature, linked tickets, Confluence) - [ ] Step 3: Load reference data for calibration - [ ] Step 4: Run scrum-poker council session - [ ] Step 5: Present estimate with rationale ``` ### Step 1: Gather ticket context Use the Atlassian MCP (read-only) to collect: 1. **Issue details** — `jira_get_issue` with the ticket key. Extract: summary, description, issue type, priority, labels, components, current story points (if any), acceptance criteria. 2. **Comments** — `jira_get_comments` for team discussion and context. 3. **Changelog** — `jira_get_changelog` to see if story points were previously set, changed, or debated. ### Step 2: Gather related context 1. **Parent feature/epic** — if the issue has a Feature Link or Epic Link, fetch it with `jira_get_issue` to understand the broader scope. 2. **Linked tickets** — follow issue links (blocks, relates-to, split-from) to understand dependencies and prior work. Limit to 3-5 most relevant links. 3. **Confluence context** — if the ticket references Confluence pages or has remote links, fetch up to 2 pages for additional design/requirements context using `confluence_get_page`. 4. **Simil