skills.rest
edumesones
edumesonesCOMMUNITY
Explore all skills by this author →
GitHub

architecture-designer

Creates Architecture Decision Records and architecture overviews from project requirements.

Updated Feb 5, 2026
Search Tags:#architecture#documentation#ADR#project-management#system-design#architecture-decision
One-click install
npx skills add https://github.com/edumesones/azure--demo --skill architecture-designer-edumesones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/edumesones/azure--demo/tree/main/.claude/skills/architecture-designer
Command: npx skills add https://github.com/edumesones/azure--demo --skill architecture-designer-edumesones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams convert vague project requirements into concrete architectural decisions and ADRs, providing a clear architectural contract.

Core Features & Use Cases

  • Architecture overview: Create a high-level system diagram and a concise architectural overview.
  • ADRs: Produce Architecture Decision Records documenting key decisions and trade-offs.
  • Project alignment: Ensure architecture decisions align with project goals and constraints; generate project-context docs from initial interviews to implementation readiness.

Quick Start

Use this skill to define the architecture for your project and produce ADRs and an architecture overview.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I create Architecture Decision Records from project requirements?▼

You create Architecture Decision Records by guiding project context interviews to formalize technology decisions, trade-offs, and constraints into structured ADR documentation. This skill enforces structured ADR creation to align decisions with documented project goals.

What is the best way to document architectural decisions and trade-offs?▼

Documenting architectural decisions is best handled by creating formal Architecture Decision Records that capture key decisions, trade-offs, and project alignment. This approach provides a clear architectural contract for the team.

How do I turn vague system design requirements into a concrete architecture overview?▼

You turn vague requirements into a concrete architecture overview by generating project-context docs from initial interviews. This process produces a high-level system diagram and ensures alignment with project goals and constraints.

When do I need formal ADR documentation for my project?▼

You need formal ADR documentation when converting project requirements into concrete architectural decisions. It enforces structured decision creation and formal documentation, providing a clear architectural contract from initial context to implementation readiness.

Can I ensure technology decisions align with documented project goals and constraints?▼

You can ensure technology decisions align with project goals and constraints by formalizing them within Architecture Decision Records. This skill enforces alignment by documenting decisions against the established project context and architectural contract.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
cy-walicy-wali

architecture

Generate Architecture Decision Records documenting technology decisions with trade-offs.

Community
Advanced
ExsyDevExsyDev

aif-roadmap

Create and update project roadmaps stored at .ai-factory/ROADMAP.md.

Community
Advanced
augustsclaugustscl
2

architecture-designer

Design system architectures and document ADRs for distributed systems.

Community
Advanced