What problem does it solve? Engineering teams often lack a written north-star architecture, making it hard to judge whether daily changes move the system in the right direction. This Skill guides the authoring of a technical vision document that captures the target architecture, the honest current-vs-target gap, an ordered migration path, and the anti-scope of roads deliberately not taken. ## Core Features & Use Cases - Section-by-section authoring: Walks through the shipped VISION-TEMPLATE.md scaffold interactively rather than dropping an empty template on the user. - Role-bound execution: Runs as the tech-lead Role via runs-as, and works standalone without requiring an Orchestrator. - Grounded in repo context: Anchors claims in OMNIGRID-CONTEXT.md domain language and existing ADRs in omnigrid/artifacts/adrs/. - Artifact regeneration contract: Writes a footer-signed vision to omnigrid/artifacts/architecture/vision.md, archiving prior canonical copies and never overwriting hand-owned files. - Use Case: A tech lead kicking off a re-platforming effort runs the skill to produce a signed vision.md that the team references when reviewing architecture decisions and planning migrations. ## Quick Start Ask the assistant to run /tech-vision for the whole repository or a specific system area to author the architecture vision document.
