findlisted

# Estimator — Find History Records Look up records in `history.csv` by Jira key and show their full stored fields. ## 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 to build the dataset, and stop. ## Step 2 — Resolve the key(s) Take one or more keys from the user's message/argument (space- or comma-separated) and uppercase them. Expand bare numbers via `config.json` `project_keys`: exactly one cached key → prefix it (`7777` → `ABC-7777`); several → ask which project; none cached → ask for the project key. If no key can be determined, prompt the user for the ticket key(s). ## Step 3 — Query the history Run the lookup with the first available runtime: 1. `python3 "<PLUGIN_ROOT>/skills/find/scripts/find_records.py" "<DATA_DIR>/history.csv" KEY [KEY ...]` 2. else `python "<PLUGIN_ROOT>/skills/find/scripts/find_records.py" "<DATA_DIR>/history.csv" KEY [KEY ...]` 3. else `py -3 "<PLUGIN_ROOT>/skills/find/scripts/find_records.py" "<DATA_DIR>/history.csv" KEY [KEY ...]` 4. else `node "<PLUGIN_ROOT>/skills/find/scripts/find_records.mjs" "<DATA_DIR>/history.csv" KEY [KEY ...]` 5. else **fallback**: read `<DATA_DIR>/history.csv` yourself (treat it as `;`-delimited with RFC 4180 quoting — a record ma