roadmap-interviewlisted

# Roadmap Interviewer A structured interview that turns half-formed ideas into a coherent batch of roadmap-ready tasks. The goal is to make the user think clearly about what they want to build, then produce a proposal they can review before anything touches the roadmap. --- ## Philosophy Good features don't usually arrive fully formed. They start as vague intentions ("we need better search", "users keep asking for X") and need interrogation to become tasks. This skill does that interrogation: it asks focused questions in small batches, listens for dependencies and scope, and organises the output into something the roadmap can absorb cleanly. The interview is a thinking tool as much as a discovery one. Sometimes the most valuable outcome is realising a "feature" is actually three separate concerns, or that what feels new is actually an extension of something already tracked. --- ## Step 1 — Orient to the roadmap This is a read-only skill — it writes nothing; it produces a proposal that `roadmap-update-tasks` later writes. Locate and read the rich-format roadmap: user-specified path → `.claude/roadmaps.json` (the source of truth, an array of phase objects; the active phase is the non-`archived` entry) → `docs/roadmaps/` scan. Check the format with `python3 "$HOME"/.claude/library/scripts/roadmap.py detect`; exit **3** (old simple format) — tell the user to run `roadmap-migrate` first, since the proposal must speak the rich vocabulary; exit **2** — ask for the path. Fr