addlisted

# Estimator — Add Tickets to History Record specific tickets in `history.csv` by Jira key, fetched live from Jira, without re-running `/sync`. For filling in a few missing/new records. Adds whole records — field-level editing is `/edit`; an existing record is **overridden** (replaced with fresh Jira data) only after explicit confirmation. ## Read-only Jira access This skill treats Jira purely as a **data source**. Use only read operations — `atlassianUserInfo`, `getAccessibleAtlassianResources`, project/field metadata, `searchJiraIssuesUsingJql`, `getJiraIssue`, `getJiraIssueRemoteIssueLinks`. You MUST NOT call any operation that creates, edits, transitions, comments on, links, assigns, deletes, or logs work against Jira issues (or writes to Confluence). If a step seems to require a write, stop and tell the user instead of proceeding. ## Data location Resolve `<DATA_DIR>` as the other skills do — the per-user data dir `~/.estimator`: - Bash: `DATA_DIR="$HOME/.estimator"` - PowerShell: `$DATA_DIR = Join-Path $env:USERPROFILE '.estimator'` ## Step 1 — Preflight Resolve `<DATA_DIR>`. If `<DATA_DIR>/history.csv` does not exist, tell the user to run `/sync` first (or use the `import` skill) and stop. Verify the Atlassian MCP is connected (`atlassianUserInfo`); if not, tell the user to connect it (`/mcp`) and stop. Read `config.json` for `story_point_field_id` and `project_keys`. ## Step 2 — Resolve the key(s) Take one or more keys from the user's message/argument (space- or