The roadmap your team actually executes from.

Three phase lanes (Foundation, Build, Validate) with task cards inside each lane. Every task carries a title, a definition-of-done, a phase chip, and dependency arrows linking it back to whatever blueprint produced it. No timelines you'll never hit — just sequence and DoD.

Without DoD, a task is a wish. With DoD, your team knows when the task is shippable — which means the roadmap stops being a vibes-based to-do list and starts being a contract. Gaplyze emits DoD for every task because the blueprint already encodes the deliverable.

Each task carries an explicit upstream-task reference. The board shows the dependency as an arrow between cards; the export shows it as a parent-task ID. You can spot the critical path without a Gantt chart.

Yes. Auto-generation gives you the first pass; you keep edit control on every task, DoD, dependency, and phase assignment. Manual edits are preserved when you regenerate — only untouched tasks are re-derived.

Regenerating the roadmap picks up the blueprint diff and applies it to the affected tasks. Untouched tasks stay put; tasks the blueprint dropped get archived (not deleted); new tasks slot into the appropriate phase. You always see what changed before you accept the update.

Roadmaps export as Markdown and structured JSON — the JSON is shaped so it maps cleanly into Linear, Jira, Notion, or any other tool that accepts a task list with dependencies and a definition-of-done.