milestonelisted

# Milestone v2 — Persistent Development Context **Pattern**: SKILL.md = **Process** (state machine, checkpoints). `references/` = **Tool** (exact procedures, decision trees). Body teaches WHEN; references teach HOW. ## Overview Portable skill for multi-session development tracking. Manages state (`[ ]`/`[>]`/`[~]`/`[x]`/`[-]`), history (`## Contexto`), decisions, and memory snapshots. Zero external dependencies. Integrations (Monday/Jira/Linear/Slack) live in separate skills that observe `.milestones/*.md` via hooks. **Optional team mode (R13 + R14)**: opt-in via `.milestones/config.yml` makes the milestone a single shared source of truth git-synced to a canonical branch (R13) AND requires an atomic claim before starting any subtask so two members can never accidentally pick the same one (R14) — degrades to no-op when not configured, so the zero-dependency promise still holds. **Use when**: multi-session work OR need to resume context OR architectural decisions to remember. Otherwise → TodoWrite/Plan. ## Critical anti-patterns (TOP 3 — full list → [`references/anti-patterns.md`](references/anti-patterns.md)) 1. **NEVER mark `[x]` without explicit human approval post-QA.** "pasa a la siguiente" / "ok" / "listo" are NOT approval — only "apruebo X.Y" / "marca como terminada" / "confirmed" count. Failed QA → stays `[~]`, never reverts. 2. **NEVER flip state based on intent.** Only advance AFTER verified evidence on disk (grep confirms symbol/route/method, git status lists f