tech-vision

Guide operators through a template-driven interview to generate a vision.md with a Mermaid diagram.

Updated Apr 15, 2026

Search Tags:#template #architecture #documentation #mermaid #interview #vision

Ready to run

npx skills add https://github.com/AAbdulghany/fms --skill tech-vision-aabdulghany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-vision
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/tech-vision
Command: npx skills add https://github.com/AAbdulghany/fms --skill tech-vision-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting a clear, stakeholder-aligned architecture vision is hard without a structured process to capture scope, decisions, and future state.

Core Features & Use Cases

Interactive interview that walks operators through the template sections (Scope, Principles, Target-state architecture, Current state vs target state, Migration path, anti-scope, and cadence) to produce a ready-to-commit vision document.
Auto-generates a Markdown architecture vision file (vision.md) with an embedded Mermaid diagram and validation for anti-scope and migration data.
Use Case: a platform team defines a new system's north-star, documents decisions consistently, and shares a uniform vision across projects.

Quick Start

Invoke the /tech-vision skill for a project to begin the interactive interview and generate the architecture vision document.

Frequently Asked Questions about tech-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create an architecture vision document with a structured template?▼

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.

What is an anti-scope in architecture documentation and why is it validated?▼

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.

How do I generate a Mermaid diagram for a target state architecture?▼

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.

What's the best way to document a migration path for software architecture?▼

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.

Can I define project cadence and principles in an architecture vision markdown file?▼

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.

Does architecture vision authoring require external prompts or dependencies?▼

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.