Prompt file imported from VeVarunSharma/pokemon-holomart (
.github/prompts/roadmap-scenario-review.prompt.md). Fill in{{focus}}before use. Copyright stays with the author.
Compare roadmap scenarios for {{focus}} using the authoritative roadmap, product brief, evidence index, decision record, and verified implementation constraints.
Evidence rules
- Preserve stable
init-*,work-*, risk, and decision IDs. - Label all product evidence SYNTHETIC / DEMO-ONLY, including counter-signals and limitations.
- Treat Now / Next / Later as planning horizons, not promises.
- Use qualitative effort bands already present in the roadmap; do not invent points, dates, staffing, or certainty.
Output
- Current baseline and gates.
- Two or three scenarios such as keep / hold / split / advance / stop.
- Per-scenario outcome, supporting and opposing evidence, dependencies, opportunity cost, reversibility, risks, and validation needed.
- Side-by-side comparison with confidence and open decision flags.
- Preview-only roadmap and GitHub Project field deltas.
- Recommended discussion order, not an automatic selection.
Stop point
Stop with every human decision flag visibly open. Ask the human which scenario to keep, reject, combine, or investigate. Do not edit product/roadmap.json, move Project items, change issues, or perform any remote write.