ijfw-new-milestone

# IJFW New Milestone Kick off a new milestone cycle on an existing project. Brownfield equivalent of project bootstrap: project exists, prior milestones shipped, you need a scoped plan for the next iteration. Domain-agnostic. Works for software releases (v1.2 → v1.3), book chapters (Ch 4 → Ch 5), campaign waves (Wave 2 → Wave 3), design-system tiers (Foundation → Components → Patterns). Optional `$ARGUMENTS`: milestone name (e.g. `v1.6 Notifications`, `Chapter 5: Adversarial Models`). Ask inline if absent. ## 1 — Load prior context Read in order: - `.planning/PROJECT.md` — core value, validated outcomes, decisions - `.planning/ROADMAP.md` — what shipped, last milestone number/name - `.planning/MILESTONES.md` — historical log (if present) - `.planning/STATE.md` — pending todos, blockers carried forward - Latest `.planning/<prior-milestone>/LEARNINGS.md` (if present) — dispatch `ijfw-extract-learnings` agent on the prior milestone first if missing; learnings inform what to do differently this cycle. If `.planning/ROADMAP.md` is absent, dispatch `ijfw-roadmapper` agent to scaffold one from `PROJECT.md`, then resume here. ## 2 — Determine next milestone identifier Parse the last milestone from `MILESTONES.md` or `ROADMAP.md`. Suggest the next per project convention: - Semver: `v1.5 → v1.6` (minor) / `v1.5 → v2.0` (major) - Chapter / Wave: `N → N+1` - Free-form: ask the user Confirm before writing anything. ## 3 — Gather scope (adaptive) Ask one open question: `What do ...