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 you want to ship in this milestone? (one sentence)

Then probe by domain bucket (pick what fits, skip the rest):

• Capabilities — new functionality / features / chapters / campaign assets
• Quality — coverage, perf, accessibility, edit passes, brand consistency
• Trust — security, audits, fact-checks, compliance, source alignment
• Ecosystem — integrations, partners, distribution channels, platform support
• Reduction — deprecations, cuts, tightening, scope-creep kills

Per activated bucket ask: Table stakes vs differentiators? Table stakes go in; differentiators debated.

If prior LEARNINGS.md exists, surface its top 3 "do differently" items and ask which to act on.

4 — Verify understanding before writing

Present a summary block and ask for confirmation:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 IJFW ► MILESTONE SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Milestone: <identifier> — <name>

Goal: <one sentence>

In scope:
  - <bucket>: <item 1>, <item 2>
  - <bucket>: <item 3>

Out of scope (explicit):
  - <thing user declined>

Learnings applied:
  - <from prior LEARNINGS.md>

Success criteria (top-level):
  1. <observable outcome>
  2. <observable outcome>
  3. <observable outcome>

Ask: "Does this capture it? (looks good / adjust)". Loop until confirmed.

5 — Write artifacts

Atomically create/update:

• .planning/<milestone>/HANDOFF.md — skeleton with: identifier, goal, scope buckets, success criteria, "what shipped last", "what's deferred from last", initial plan-item list. This is the durable per-milestone home.
• .planning/PROJECT.md — append ## Current Milestone: <id> block with goal + target buckets. Update the footer timestamp.
• .planning/STATE.md — reset status to planning, zero progress counters, preserve accumulated context (decisions, blockers, todos).
• .planning/ROADMAP.md — append milestone entry with placeholder phase list (filled in step 6).

HANDOFF.md skeleton:

# Handoff — <Milestone Identifier>

Updated: <ISO date>
Goal: <one sentence>

## Inputs
- Prior milestone: <id> (LEARNINGS: <path or "n/a">)
- Carried forward: <pending blockers from prior STATE.md>

## Scope (in)
- <bucket>: <item>, <item>
- <bucket>: <item>

## Out of scope (explicit)
- <item> — <reason>

## Success criteria
1. <observable>
2. <observable>
3. <observable>

## Plan items (filled by ijfw-spec-phase + ijfw-discuss-phase per item)
- [ ] <item-id>: <title> — status: pending
- [ ] <item-id>: <title> — status: pending

## Resume protocol
Next session: read this file, run `/ijfw-execute <item-id>` for the first
pending item. Each item completes atomically with its own commit.