architecture

Document architecture decisions and rationale with ADR templates and trade-off analysis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thimmarques/gestao-inteligente --skill architecture-thimmarques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/thimmarques/gestao-inteligente/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/thimmarques/gestao-inteligente --skill architecture-thimmarques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making at scale requires structured capture of context, options, trade-offs, and rationale to avoid repeated debates and ensure traceability.

Core Features & Use Cases

  • ADR templates and pattern references for consistent decisions
  • Trade-off analysis with rationale and consequences
  • Guidance to integrate ADRs into team workflows and documentation

Quick Start

Draft an ADR for a current design decision including context, options, decision, and consequences.

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 avoid repeated debates?

You can document architecture decisions using ADR templates to capture context, options, trade-offs, and rationale, ensuring traceability and avoiding repeated team debates.

What is an ADR and when do I need to write one?

An ADR is an Architecture Decision Record used to document context, trade-offs, and consequences. You need an ADR during system redesigns and when making major technology choices.

How do I conduct trade-off analysis for a major technology choice?

Conduct trade-off analysis for a technology choice by evaluating options against context and recording the rationale and consequences in a structured ADR template.

Can I integrate architecture decision records into existing team workflows?

Yes, this framework provides guidance to integrate ADRs into team workflows and design documentation, ensuring consistent decision recording across the organization.

What is the best way to structure design documentation for system redesigns?

The best way to structure design documentation is by using ADR-driven frameworks that capture context, decision rationale, and consequences for major architectural choices.