← ClaudeAtlas

milestonelisted

Use when tracking multi-session development work, resuming context from previous conversations, planning phased features, or capturing architectural decisions. Triggers: 'milestone', 'retomar', 'dónde lo dejé', 'seguimos con', 'estado del proyecto', 'qué falta', 'siguiente tarea', 'qué hicimos la última vez', 'pendientes', 'resume where we left off', 'what's left', 'mark as done', 'close milestone', 'sync milestones', 'audit the project', phased feature planning, subtask tracking, work-in-progress recovery. Portable across projects — no external dependencies. Commands: /milestone, /milestone <name>, /milestone init, /milestone sync, /milestone start, /milestone done, /milestone update.
j4rk0r/claude-skills · ★ 2 · AI & Automation · score 76
Install: claude install-skill j4rk0r/claude-skills
# 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). Además, un **sync de índice** (H4, git-sync.md §12) descubre milestones que otro creó antes de listar o crear: al hacer `/milestone init` avisa si el nombre ya existe (y quién lo creó, cuándo) en vez de duplicar; al hacer `/milestone` (list) muestra los milestones remotos que aún no tienes en local. Todo degrada a no-op cuando no está configurado, así que la promesa zero-dependency se mantiene. **Optional central storage (R13 §2b)**: opt-in by placing the config in the central memories repo (`~/.claude/projects/<key>/milestones/config.yml`) instead of the project repo — the client repo stays 100% clean of internal planning. **Use when**: multi-session work OR need to resume context