write-roadmaplisted

# Roadmap Writer ## When to Use Use this skill when you need to translate strategy and OKRs into a clear, communicable picture of what the team is working on and why. It adds the most value when: - **Starting a planning cycle** — turn a freshly written strategy or set of OKRs into a roadmap the team and stakeholders can reason about. Use immediately after `write-okrs` to close the loop from strategy through measurement to planned work. - **Communicating priorities to stakeholders** — when leadership, sales, or external partners ask "what are you building and when?", a horizon-based roadmap gives an honest, durable answer without over-committing to specific dates. - **Aligning engineering on what's coming** — engineers need enough forward visibility to make good technical decisions (avoiding premature optimisation, planning for capacity, flagging risks early). A Now/Next/Later roadmap provides that signal without locking in requirements before they're understood. ## Input Format The skill scans the current project directory for `STRATEGY.md` and any OKR documents automatically. If found, it reads strategy pillars and Key Results to derive roadmap themes. You can also provide: **Path to strategy and OKR documents:** ``` Strategy: ./STRATEGY.md OKRs: ./OKRs-Q2-2026.md ``` **Pasted priorities or strategic pillars:** ``` Pillar 1: Improve activation for self-serve sign-ups Pillar 2: Expand into the mid-market segment Pillar 3: Lay the compliance foundation for enterprise de