| name | roadmap |
| description | Build or update the roadmap — epics on a Now/Next/Later horizon on the board, dated only as far as honesty allows, with the narrative stakeholders can repeat. |
| disable-model-invocation | true |
Roadmap
Keep one roadmap: the board's roadmap view over epics. This ritual shapes it and keeps it honest — a roadmap that promises dates it can't know is a stakeholder incident scheduled in advance.
1. Read the present
Via the board skill: active epics and their sub-issue progress, current iteration load, and delivery pace over the last 2–3 iterations (the only forecasting input that isn't opinion).
2. Shape the horizon
Place every epic in one of three bands — the band is the commitment level:
- Now — in the current or next iteration; carries iteration assignments and real dates.
- Next — after Now; ordered relative to each other, dated only to a quarter.
- Later — direction, not commitment; no dates, and pruned each session ("would we still do this?").
Anything more precise than the band allows gets pushed back into the epic body as a note. Check Now against measured pace: a Now band bigger than two iterations of measured delivery is a wish, not a plan — say so and force the cut with the Product Manager's priority order.
3. Write the narrative
Three sentences a stakeholder can repeat: what's landing now, what's next and why that order, what we deliberately aren't doing. Put it in the roadmap view's description (or the epic-index issue).
Done when: every open epic sits in exactly one band, no Later item carries a date, target dates exist only in Now (and quarter-tags in Next), and the narrative matches what the bands actually say.
