tech-vision

Create an architecture vision document by interactively collecting target-state, migration path, and anti-scope content section-by-section, ensuring honest governance through explicit exclusions and concrete milestones before finalizing the output.

You validate a Mermaid C4 diagram in architecture documentation by applying Mermaid lint validation to the target-state section, ensuring the C4 block is syntactically valid before the file write is finalized.

An anti-scope section in a technical architecture vision explicitly defines what is excluded from the project scope, forcing honest governance and providing reconsider guidance to prevent architecture docs from becoming aspirational stubs.

Yes, you can use a custom SDLC template for architecture vision authoring. The system discovers template section headings from the resolved template, matching the interview structure to either a framework default or a custom override.

Generate a production-ready architecture vision for new system onboarding by running an interactive interview process that populates a resolved vision.md file, aligning target-state architecture, migration milestones, and anti-scope to an SDLC template.

If an architecture vision file already exists, the write behavior is guarded to prevent overwriting existing outputs, ensuring your current architecture documentation remains protected during the interactive authoring process.