Produces an opinionated 12-24 month technical vision for a domain — honest current state, business context, a concrete vision, 3-5 architectural principles, 4-6 key initiatives, what to stop doing, success metrics, and risks. Use when the user says "write a technical vision/strategy", "where should our architecture go", "north star for [domain]", or asks for multi-year engineering direction. Use this for the multi-year direction across systems; use system-design-document for one system's blueprint, technology-radar for the adopt/hold tooling calls, and a roadmap for quarterly execution rather than direction.
