architecture

Frame architectural decisions using a structured ADR-based framework.

Updated Feb 22, 2026

Search Tags:#architecture #documentation #adr #patterns #trade-offs #decision-making #architecture-review

Ready to run

npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill architecture-gelsonsimoes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/gelsonsimoes/wms-verticalparts/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/gelsonsimoes/wms-verticalparts --skill architecture-gelsonsimoes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable framework for making architecture decisions by structuring requirements analysis, trade-off evaluation, and ADR documentation. This helps teams capture rationale, compare options, and communicate decisions clearly.

Core Features & Use Cases

Structured ADR workflow for documenting decisions
Templates for context, options, decisions, and trade-offs
Reference materials and patterns to inform decisions

Quick Start

Outline your architecture decision and draft an ADR using this framework.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architecture decisions and trade-offs?▼

Document architecture decisions by framing context, comparing options, and capturing rationale using a structured ADR template. This framework guides you through requirements analysis and trade-off evaluation to communicate system designs clearly.

What is an ADR and when do I need one for system design?▼

An ADR is an Architecture Decision Record used to capture the context, options, and rationale behind a system design choice. You need one to ensure repeatable decision-making and preserve trade-off evaluation for future architecture reviews.

How do I evaluate architecture patterns and options for my project?▼

Evaluate architecture patterns by applying a structured framework to compare options against your specific requirements. This process identifies trade-offs and risks, ensuring your decision-making is backed by clear context and documented rationale.

Can I use this framework to conduct an architecture review?▼

Yes, you can use this ADR-based framework to conduct an architecture review. It structures requirements analysis and decision capture, allowing teams to systematically assess trade-offs, reference patterns, and mitigate risks across existing system designs.

What is the best way to structure requirements analysis for architecture decisions?▼

The best way to structure requirements analysis is to use a repeatable ADR workflow that separates context, options, and decisions. This approach frames trade-offs and risk mitigation, ensuring your architecture decisions are documented consistently.

Why does my team struggle to communicate architecture decisions clearly?▼

Teams struggle to communicate architecture decisions clearly when they lack a repeatable framework for documenting context and rationale. Using structured ADR templates ensures trade-offs and options are captured, making system design decisions easy to understand.