roadmap

# foreman:roadmap — pick, add to, correct, review, or check the project roadmap All reads/writes to `ROADMAP.jsonl` at the project root go through `${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js` — never `Read`/`Edit` the file directly, the script enforces id computation and parse-before/after-write mechanically — run it with `--help` for the command shapes. Read the **Fields** section of `${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md` if you need field semantics beyond what's obvious from the names. **Pre-check**: if `ROADMAP.jsonl` doesn't exist at the project root, tell the user to run `/foreman:init` first and stop here. --- ## Call 1 — menu **Q1** — "What do you need?" Options: - `Pick the next task` — read the roadmap, reason about what to work on next, craft a handoff prompt for it. - `Add a task` — append a new entry to the roadmap. - `Correct a task` — fix a stale title, why, what, kind, or planned files on an entry that already exists. - `Review status` — read-only summary of where every task stands. `AskUserQuestion` takes four options at most, so the structural doctor is reached by asking for it rather than from this menu — the routing just below carries the phrasings that get there. If args were provided and read like a task description rather than a question, treat it as a seed for "Add a task" and skip this call. If they read like a pick request or a hint about what to pick ("what's next on auth", "something quick I can finish today"), go straight to "Pick the n...