architecture

Document architecture decisions with ADR templates and decision frameworks.

Updated Apr 30, 2026

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

Ready to run

npx skills add https://github.com/zerielribeiro/sistema-pecas --skill architecture-zerielribeiro

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users develop and document architectural decisions for software systems, ensuring clarity and traceability in system design.

Core Features & Use Cases

Requirements analysis and trade-off evaluation: Guides users through analyzing demands and evaluating different architectural options.
ADR documentation: Facilitates recording rationales and decisions to maintain consistency and justify architecture choices.
Use Case: When designing a new microservices platform, use this Skill to analyze options, document trade-offs, and record architectural decisions systematically.

Quick Start

Use the architecture Skill to analyze your system requirements and document architecture decisions with detailed trade-offs.

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 architecture decisions?▼

To document architecture decisions, analyze your system requirements, evaluate design trade-offs, and record the rationale using ADR templates. This framework guides you through structuring decisions to maintain consistency and justify choices for scalable platforms.

How do I evaluate trade-offs when designing a microservices architecture?▼

To evaluate microservices architecture trade-offs, use a structured decision framework to analyze demands against different design options. This process helps you compare scalability and maintainability impacts before documenting the final rationale in an ADR.

Does this architecture decision framework work without external dependencies?▼

The architecture framework focuses on requirements analysis and trade-off evaluation for system design rather than implementation. It distinguishes itself by systematically documenting the decision-making rationale and ensuring traceability through ADRs.

When should I not use a structured architecture decision framework?▼

You should avoid a structured architecture decision framework for trivial system design changes that do not involve significant trade-offs. If a project lacks scalability or compliance requirements, formal ADR documentation may introduce unnecessary overhead.