survey

# foreman:survey — ground-truth the roadmap's near-term candidates This is the one Foreman flow that deliberately investigates the codebase against the roadmap. `foreman:roadmap`'s pick-next-task branch explicitly does **not** do this — see the 0.4.4-alpha changelog entry, where doing exactly this at pick time burned ~100k tokens on every invocation. Keeping it a separate, explicitly-triggered skill is what makes both halves cheap: the fast path stays mechanical, and ground-truthing only runs when someone actually asks for it. All reads/writes to `ROADMAP.jsonl` go through `${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js` — never `Read`/`Edit` the file directly — run it with `--help` for the command shapes. Read the **Fields** section of `${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md` for field semantics. **Pre-check**: if `ROADMAP.jsonl` doesn't exist at the project root, tell the user to run `/foreman:init` first and stop here. --- ## 1. Pick the scope <!-- [Foreman: 141] --> If a caller handed over a set of ids, that set **is** the scope — args naming specific tasks, or **Reconcile and pick**'s near-term set (`foreman:roadmap`'s pick branch derives it from one `next-candidates --menu` result: the candidate rows plus the `in_progress` and `awaiting_acceptance` rows). Run `list --ids <those ids>`, drop any that don't exist or are terminal (`done`/`dropped`/`rejected` — history its commits already describe) and say which you dropped, and skip the `next-candidates` call below. Scopin...