tech-vision

An architecture vision document is generated through an interactive interview that captures scope, principles, target state, migration, anti-scope, and cadence to produce a ready-to-commit vision.md file.

An anti-scope defines what a project explicitly excludes. Architecture documentation validates anti-scope items during generation to ensure consistent stakeholder alignment on project boundaries and limitations.

To generate a Mermaid diagram, you complete an interactive interview covering your target state architecture. The Mermaid diagram is then automatically generated and embedded into your final vision.md document.

The best way to document a migration path is using a structured template that validates your migration data alongside current and target state architectures, ensuring consistent and complete project documentation.

Yes, you can define project cadence and principles in an architecture vision markdown file. A guided interview walks you through these specific multi-section topics to capture and format your decisions consistently.

Architecture vision authoring requires no external prompts or dependencies. The interview operates independently using standard inputs to validate anti-scope items, migration paths, and generated diagrams.