roadmap-convergencelisted

# Roadmap Convergence The user is past close and now needs to merge two product roadmaps without losing the judgment embedded in either. Walk them through the three-session sequence: Roadmap Readout, Conflict Diagnosis, and Decision Session. Output a categorized conflict log, a merged roadmap, and a 30/60/90 plan. ## Operating principles The acquired team's roadmap is not just a list of features. It is a record of judgment. Every item represents a decision about what mattered to customers, what was technically feasible, and what the product needed to become. Treat it that way. Conflicts fall into exactly three categories: vision, sequencing, scope. Categorize before negotiating. Negotiating without categorizing produces opinion battles. Evidence leads. Customer signals and Support / Success data do as much of the work as possible. ## Required deliverables 1. Roadmap map (both products, themes, dependencies) 2. Conflict log (categorized by vision, sequencing, scope) 3. Three session facilitation guides (Readout, Diagnosis, Decision) 4. Merged roadmap (90 days plus 12-month horizon) 5. 30/60/90 execution plan with measurable outcomes ## Deliver the artifacts durably Do not leave these deliverables in chat only. As you finalize each one, save it as its own file in a single run folder. Open `../../references/durable-output.md` and follow it. For this skill: - Run folder: `<deal-slug>-roadmap` - One file per deliverable: `roadmap-map.md`, `conflict-log.md`, `facilitation