Roadmap

Turn goals, candidate ideas, tickets, findings, and design docs into a high-level view of what's coming up.

A roadmap is direction + prioritization + dependencies. It says what capabilities, outcomes, or strategic tracks are likely next, why they matter, and what must happen before they are real. It is not a wish list, transcript, date promise, backlog dump, sprint plan, or implementation plan.

Default roadmap items are outcomes/capabilities/features. Use Agile-shaped nouns — epics, milestones, phases — only when they clarify sequencing or match the project's vocabulary. Features and epics describe what changes; milestones and phases describe ordering, gates, or release boundaries.

Stay one altitude above writing-plans: decide ordering, slices, gates, and handoffs; do not design unresolved internals or prescribe code. If one item needs product shaping, hand it to brainstorm. If technical choices are unresolved, hand it to design-discussion. If implementation is decided, hand it to writing-plans.

Never modify source code. Write only roadmap artifacts unless the user explicitly asks for downstream artifacts.

Workflow

Phase 1 — Set the altitude

Identify the roadmap's audience and horizon: