roadmap

# foreman:roadmap — pick, add to, or review 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. Skim `${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. - `Review status` — read-only summary of where every task stands. 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 next task" with the hint in hand — that branch says what to do with it. --- ## Branch: Pick the next task **This branch does not investigate the codebase. At all.** No `Read`, no `Grep`, no exploring files to confirm or expand what an entry says. The picked entry's own fields are the only input to the prompt. Verifying those claims against reality is the handed-off session's job, at...