Technology roadmap planning and narrative for a tech manager. Triggers on "roadmap", "plan the next quarter", "sequence these initiatives", "what should we do first", "prioritise this backlog", "roadmap narrative", "build a roadmap", "roadmap for [project/team]". Takes initiatives, constraints, and strategic goals — produces narrative-ready roadmap with themes, sequencing rationale, dependencies, trade-offs in business language. Adapts to audience (exec narrative, team planning doc, stakeholder one-pager).
Produce a roadmap from a set of initiatives and constraints. Make it narrative-ready, not just a list.
references/roadmap-formats.md for the target format template.When sequencing initiatives, consider:
Make sequencing rationale explicit — "Initiative B comes after A because..." is more useful than just a timeline.
A good roadmap acknowledges what it's NOT doing and why. Include a "What we're not doing (and why)" section when producing exec or stakeholder formats.
Group initiatives into 2–4 themes where possible. Themes (e.g., "Platform Stability", "Customer Experience", "Compliance") make a roadmap readable and communicable. Project lists are for planning; themes are for storytelling.
references/roadmap-formats.md — Templates for exec narrative, team planning doc, and stakeholder one-pager. Read before producing output.