architecture

Document architectural decisions using ADR templates with constraints and rationale.

Updated Jan 20, 2026

Search Tags:#architecture #documentation #ADR #trade-offs #decision-making #system-design

Ready to run

npx skills add https://github.com/lchenrique/politron-ide --skill architecture-lchenrique

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for architectural decision making, enabling teams to capture requirements, compare trade-offs, and document decisions using ADRs.

Core Features & Use Cases

ADR templates and decision records to standardize architecture conversations.
Guidance for selecting patterns, evaluating constraints, and communicating rationale.
Use Case: When facing a major design choice (e.g., monolith vs microservices), use ADRs to document alternatives and outcomes.

Quick Start

Start by creating an ADR for a new subsystem, using the ADR template to capture context, options, and decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema

What is an ADR and when do I need to document architectural decisions?▼

An ADR documents architectural decisions by capturing context, constraints, alternatives, and rationale. You need ADRs when facing major design choices, such as deciding between monolith and microservices, to communicate outcomes clearly.

How do I write an ADR for system design trade-offs?▼

To write an ADR for system design, use a standardized template to capture requirements, evaluate trade-offs between alternatives, and document the final decision rationale. This enforces consistent architecture conversations across the team.

Can I use this ADR framework to evaluate monolith vs microservices?▼

Yes, this ADR framework guides trade-off evaluation for monolith vs microservices decisions. It enforces templates to document alternatives, constraints, and rationale, standardizing architecture conversations across software projects.

What's the best way to standardize architecture decision workflows across software projects?▼

The best way to standardize architecture decision workflows is to enforce ADR templates that capture requirements and rationale. This framework guides pattern selection and ensures consistent communication of constraints and alternatives.

When should I not use an ADR-driven approach for documentation?▼

You should not use an ADR-driven approach for minor implementation details that lack significant trade-offs. ADRs are designed for major architectural decisions where documenting constraints, alternatives, and rationale provides ongoing project value.