architecture

Document architectural decisions using ADR templates with context and rationale.

Updated Dec 22, 2025

Search Tags:#architecture #documentation #patterns #framework #ADR #trade-offs #decision-records

Ready to run

npx skills add https://github.com/alaminmain/DoorAuthServer --skill architecture-alaminmain

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework to analyze requirements, evaluate trade-offs, and document architectural decisions using ADRs. It helps teams make consistent, justifiable design choices and capture rationale for future reference.

Core Features & Use Cases

Architectural Decision Records (ADR) templates and guidance to document context, options, decisions, and consequences.
Trade-off analysis templates to compare alternatives and capture rationale.
Pattern and pattern-selection guidance to choose appropriate architecture patterns for different project contexts.
When to use: during early design, major tech decisions, or when migrating between architectures (e.g., monolith to microservices).

Quick Start

To begin, create an architectural decision record using the ADR template, document at least one major decision with context, options, and rationale, and reuse this framework for ongoing design decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I document architectural decisions for my project?▼

Document architectural decisions using Architectural Decision Records (ADR) to capture context, options, rationale, and consequences. This framework provides structured templates to evaluate trade-offs and justify design choices for future reference across projects.

What is the best way to evaluate architecture trade-offs during early design?▼

Evaluate architecture trade-offs using structured templates to compare alternatives and capture rationale. This approach applies pattern-selection guidance to help teams make consistent, justifiable design choices during early development or major technology decisions.

Can I use ADR documentation when migrating from a monolith to microservices?▼

Yes, ADR documentation supports architecture migrations from monoliths to microservices. It provides a framework to analyze requirements, evaluate trade-offs, and document major design decisions with context and consequences throughout the migration process.

How do I write an architectural decision record with context and rationale?▼

Write an architectural decision record using ADR templates to document context, options, decisions, and consequences. Begin by documenting at least one major decision with its trade-off evaluation and rationale, then reuse this structure for ongoing design choices.

When do I need to create architectural decision records for my software project?▼

Create architectural decision records during early design phases, when making major technology decisions, or when migrating between architecture patterns. ADRs solve the challenge of undocumented architectural decisions by providing a structured framework to capture rationale.

Does this ADR framework work for pattern-selection guidance across different project contexts?▼

Yes, the ADR framework provides pattern-selection guidance to choose appropriate architecture patterns for different project contexts. It helps teams analyze requirements and evaluate trade-offs to ensure consistent, justifiable design choices across varying architectural scales.