--- name: Milestone Completion slug: milestone-completion category: Automation description: Milestone Completion archives a finished milestone, generates a summary, and records learnings so the next milestone can be seeded. Use it when a top-level project unit is ready to ship and needs closure artifacts. github: "https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-complete-milestone" language: JavaScript stars: 210 forks: 40 install: "npx degit https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-complete-milestone ~/.claude/skills/ijfw-complete-milestone" installs_to: ~/.claude/skills/ijfw-complete-milestone source_path: claude/skills/ijfw-complete-milestone/SKILL.md collection_size: 25 category_size: 1860 collection_url: "https://dirskills.com/collections/FerroxLabs/ijfw" added: 2026-09-04T05:26:34.147Z last_synced: 2026-09-04T05:26:34.147Z canonical_url: "https://dirskills.com/skills/milestone-completion" --- # Milestone Completion Milestone Completion archives a finished milestone, generates a summary, and records learnings so the next milestone can be seeded. Use it when a top-level project unit is ready to ship and needs closure artifacts. **Install:** ```bash npx degit https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-complete-milestone ~/.claude/skills/ijfw-complete-milestone ``` ## README Archive a completed milestone, capture what shipped, and surface the next milestone. Domain-agnostic -- a milestone may be a software release, a book part, a campaign wave, a design-system tier, or any other top-level project unit defined in `.planning/ROADMAP.md`. ## Inputs - Milestone identifier (e.g. `1.5.0`, `part-two`, `wave-3`). If the user did not name one, ask once: `Which milestone are we wrapping?` Accept any string that appears as a milestone heading in `.planning/ROADMAP.md`. ## Process 1. **Verify completion.** - Read `.planning/ROADMAP.md`. Find the milestone block for ``. - List every phase under that milestone. For each phase, check that it is marked complete (e.g. `[x]`, `status: complete`, `shipped`, or has a `SUMMARY.md` in `.planning///`). - If any phase is incomplete: surface the gap and ask `Proceed anyway and treat the open phase as deferred? (y / fix first)`. Do not auto-advance. 2. **Extract learnings (dispatch agent).** - Dispatch `ijfw-extract-learnings` with the milestone scope. The agent reads every `SUMMARY.md`, `RETRO.md`, and commit message in `.planning//**` and writes `.planning//LEARNINGS.md` (decisions, surprises, patterns, lessons). - If the agent is unavailable in this runtime, write a stub `LEARNINGS.md` with `_pending: dispatch ijfw-extract-learnings when available_` and surface the gap. 3. **Generate milestone summary (dispatch skill).** - Dispatch `ijfw-milestone-summary` with ``. The skill writes `.planning//SUMMARY.md` -- stats, accomplishments, timeline, contributors -- suitable for a release post, book-part wrap, campaign retro, or design-tier handoff. - Paste the summary's first 6 lines in-chat so the user sees what landed. 4. **Confirm with user.** - Show: milestone id, phase count, days elapsed (first → last commit in scope), first line of SUMMARY.md, first 3 LEARNINGS entries. - Ask: `Archive and seed next milestone? (yes / show full summary / hold)`. - On `hold`: stop. The artifacts remain in place; the user can re-run later. 5. **Archive artifacts.** - Move `.planning//` → `.planning/_archive//`. Preserve full directory tree. Create `.planning/_archive/` if absent. - Leave `SUMMARY.md` and `LEARNINGS.md` discoverable at `.planning/_archive//SUMMARY.md` and `.planning/_archive//LEARNINGS.md`. - Never delete -- only move. Archive is the historical record. 6. **Update ROADMAP.md.** - Collapse the milestone block to a single line: ``` - [x] -- shipped . See `.planning/_archive//SUMMARY.md`. ``` - If a next milestone is already drafted in ROADMAP.md, mark it `[ ] -- next` so it is visually surfaced. - If no next milestone exists, append: ``` - [ ] _next milestone_ -- run `/ijfw-workflow` or `/gsd-new-milestone` to define. ``` 7. **Write memory entry.** - Call `ijfw_memory_store` with: - `key`: `milestone__shipped` - `value`: first 200 chars of SUMMARY.md plus the line count of LEARNINGS.md - `tags`: `['milestone', 'shipped', ]` - If the MCP tool is unavailable, append the same entry to `.ijfw/memory/MEMORY.md` under a `## Milestones Shipped` section. 8. **Tag the commit (optional, with confirmation).** - Ask: `Tag this commit as 'milestone-'? (y / custom / skip)`. - On `y`: run `git tag -a milestone- -m ""`. - On `custom`: accept the user's tag string, then tag. - On `skip`: continue without tagging. - Never push the tag automatically. Surface the push command: `git push origin milestone-`. 9. **Commit the archive + roadmap change.** - Stage `.planning/_archive//`, `.planning/ROADMAP.md`, and `.ijfw/memory/MEMORY.md` (if touched). - Commit message: ``` chore(milestone): archive + seed next milestone - LEARNINGS.md captured ( entries) - SUMMARY.md captured ( lines) - ROADMAP.md collapsed to one-line entry - Memory: milestone__shipped ``` - Surface the SHA back to the user. 10. **Closer.** - One-line receipt: > `You went from open with phases to archived with summary, learnings, memory, and tag in minutes.` - Suggest the next move: `Run /ijfw-workflow to plan the next milestone, or /gsd-new-milestone for the full questioning loop.` ## Critical rules - **Archive before mutating.** Always move `.planning//` to `.planning/_archive//` before collapsing ROADMAP.md. If the archive move fails, abort the roadmap edit. - **One-line ROADMAP entry.** Collapsed milestones must be a single line with a link to the archive. This keeps ROADMAP.md constant-size as the project grows. - **No silent skips.** If a phase is incomplete, the user must say `proceed` -- never assume. - **Memory is mandatory.** A shipped milestone the next session can't recall is a workflow failure. If `ijfw_memory_store` is unavailable, fall back to the markdown append; never skip. - **Tags are user-gated.** Never tag without explicit `y`. Never push tags. - **Domain agnostic.** Phases in a book milestone (chapters), a campaign milestone (channels), or a design-system milestone (tiers) all use the same archive path and lifecycle -- do not hardcode software vocabulary. ## Output contract Final message to the user, in this order: 1. Receipt line (`You went from ...`). 2. Archive path (`.planning/_archive//`). 3. Commit SHA. 4. Tag (if created) and the push command. 5. Suggested next move.