architecture

Document architecture decisions using ADR templates and decision records.

Updated Nov 29, 2025

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

Ready to run

npx skills add https://github.com/thimslugga/agent-skills --skill architecture-thimslugga

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often ad hoc and hard to audit. This skill provides a repeatable ADR-driven framework to capture decisions, rationale, and traceability.

Core Features & Use Cases

ADR templates for decisions and trade-offs to document reasoning
Pattern references and decision records to standardize design choices
Use Case: Apply ADRs during architecture reviews for new systems, migrations, or platform changes

Quick Start

Provide a complete ADR for a new system design 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 to capture trade-offs and rationale?▼

You document architecture decisions using an ADR-driven framework that captures requirements, trade-offs, patterns, and rationale. This approach enforces frontmatter metadata and decision records, providing traceability for system designs from MVP to enterprise scale.

What is the best way to standardize design choices during an architecture review?▼

The best way to standardize design choices is applying pattern references and decision records via an ADR template. This enforces structured documentation of decision rationale and trade-offs during architecture reviews for new systems, migrations, or platform changes.

Can I use ADR templates for both MVP and enterprise-scale systems?▼

Yes, you can use ADR templates for both MVP and enterprise-scale systems. The framework scales across project sizes by capturing requirements, trade-offs, and rationale, ensuring architecture decisions remain auditable and traceable regardless of system complexity.

Why does my team need structured decision records instead of ad hoc architecture documentation?▼

You need structured decision records because ad hoc architecture decisions are hard to audit. A repeatable ADR-driven framework enforces frontmatter metadata and pattern references, capturing decision rationale and traceability that standardizes future design choices.

How do I start creating a complete architecture decision record for a new system design?▼

You start by providing a complete ADR for a new system design using the framework. This involves populating ADR templates with requirements, trade-offs, and rationale, while attaching optional references, assets, and scripts to support the decision.

What limitations exist when using ADRs to document architecture trade-offs?▼

A limitation of using ADRs is the strict enforcement of frontmatter metadata and templates, which may introduce overhead for rapid MVP phases. However, this constraint ensures traceability and standardized rationale for enterprise-scale architecture decisions.