league-configlisted

# League Configuration Interview the user about their fantasy league(s) and persist the answers to `leagues.md` in the project root. Every other fantasy-football-skills skill reads this file first, so a complete interview here means the user is never re-asked for scoring or roster context. ## Workflow 1. **Check for an existing `leagues.md`** in the project root. If it exists, show the current config and ask whether to update a league, add a new one, or start over. Never silently overwrite. 2. **Interview** the user, one short batch of questions at a time (not one giant wall). Collect the fields below for each league. 3. **Write `leagues.md`** using the structure in `leagues-template.md` (in this skill's directory). One `## League:` section per league. Strip the template's explanatory comments from the written file — keep it clean. 4. **Confirm** by echoing back a one-line summary per league (e.g., "Gridiron Gazette — 12-team half-PPR on Yahoo, $100 FAAB"). ## Fields to collect Required (advice quality degrades without these): - **League name** — used as the section header so multiple leagues can coexist - **Season** — record the fantasy season explicitly (for example `2026`) so dynasty, keeper, and draft contexts do not drift across years - **Platform** — `yahoo`, `espn`, `sleeper`, or `other` (drives the roster-ops browser playbooks) - **Platform league ID/key** — record the stable identifier exactly as the platform shows it (`league_id`, `league key`, Sleeper league