Resuming Roadmap Work

Overview

Front door for an ambiguous "let's continue the roadmap" request. Reads the roadmap's actual state, rechecks any logged blockers, then decides — with the user, never alone — whether the next move is documentation (batch-plan-validate) or implementation (executing-roadmap-checkpoints). Does no drafting or implementation itself.

REQUIRED BACKGROUND: roadmap-conventions (file locations, state file schema, the three-phase workflow). Hands off to batch-plan-validate (Phase 2) or executing-roadmap-checkpoints (Phase 3).

Process

1. Find the roadmap

Same rule as executing-roadmap-checkpoints step 1: named feature → docs/<slug>/*-roadmap.md; otherwise glob docs/*/*-roadmap.md; zero matches → report and stop; multiple matches → AskUserQuestion, one option per roadmap.

2. Read state

• docs/<slug>/roadmap-state.json — per-step status (roadmap-conventions → ## State File). Missing file → fall back to reading each step's checkbox and steps/<step-slug>/ folder contents directly.
• tmp/reports/batch-plan-queue.md — Phase 2 queue, if one exists for this roadmap.