architecture-design-process

Guide multi-phase software architecture projects from brainstorming to final reviews.

Updated Apr 12, 2026

Search Tags:#architecture #feasibility #traceability #domain-driven-design #use-cases #design-process #phase-gate

Ready to run

npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill architecture-design-process

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-design-process
Source: https://github.com/lygav/vladi-plugins-marketplace/tree/main/plugins/architecture-design-process/skills/architecture-design-process
Command: npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill architecture-design-process

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing complex software systems without a guided, repeatable process leads to inconsistent architectures and risk. This skill provides a structured, phase-driven approach to move from brainstorming to formal design documents with traceability and gate checks.

Core Features & Use Cases

Phase-driven workflow covering Phases 1–6: Research, Vision, Use Cases, Design by Layers, Infrastructure planning, and Final Review.
Domain-driven design primitives and explicit traceability from use cases to design components, ports, and workflows.
Built-in governance through exit criteria, iteration loops, and feasibility validation before implementation.

Quick Start

Describe your project goals and I will guide you through all six phases to produce a complete architecture design package.

Frequently Asked Questions about architecture-design-process

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

FAQPage Schema

How do I structure a software architecture design process for large multi-phase projects?▼

A software architecture design process for large projects can be structured into six phases: Research, Vision, Use Cases, Design by Layers, Infrastructure planning, and Final Review. This phase-driven workflow ensures traceability and feasibility validation through structured gate checks.

What is domain-driven design traceability in an architecture workflow?▼

Domain-driven design traceability in an architecture workflow explicitly links use cases to design components, ports, and workflows. It ensures that every architectural element maps back to a specific domain requirement, maintaining alignment throughout the design phases.

How do I validate design feasibility before implementation?▼

Validate design feasibility before implementation through structured reviews and built-in governance exit criteria. The architecture design process enforces feasibility validation at phase gates, requiring iteration loops to resolve risks before proceeding to implementation.

Can I use a phase-gate approach for architecture brainstorming to final reviews?▼

Yes, a phase-gate approach effectively guides architecture projects from initial brainstorming to final reviews. It provides repeatable phase-by-phase guidance, establishing domains and workflows while validating feasibility at each gate before moving forward.

When do I need a repeatable architecture design process?▼

You need a repeatable architecture design process when handling complex software systems to avoid inconsistent architectures and unmanaged risk. It is applicable to large, multi-phase projects where moving directly from brainstorming to formal design requires structured traceability.