skills.rest
BrunoSantanaDeveloper
BrunoSantanaDeveloperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture

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

Updated Jan 27, 2026
Search Tags:#architecture#documentation#adr#trade-offs#architecture-patterns#decision-making#requirements-analysis
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill architecture-brunosantanadeveloper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/architecture
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill architecture-brunosantanadeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document architecture decisions and rationale using ADRs to capture trade-offs and constraints.

Core Features & Use Cases

  • ADR Templates: Provides a standard structure for recording decisions.
  • Trade-off Analysis: Guides evaluation of alternatives and trade-offs.
  • Context & Documentation: Captures problem context, requirements, and constraints.
  • Documentation & Reuse: Stores decisions for future reference and audits.

Quick Start

Identify a design problem, collect constraints, and draft an ADR using the provided templates.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an ADR and how does it document architecture decisions?▼

An Architecture Decision Record (ADR) documents architecture decisions by capturing problem context, requirements, constraints, and rationale to record trade-offs for future reference and audits.

How do I write an ADR for a new software architecture pattern?▼

Identify a design problem, collect constraints, and draft an ADR using provided templates that apply to requirement analysis, trade-off evaluation, and pattern selection across projects.

When do I need to document trade-offs in architecture documentation?▼

Document trade-offs during requirement analysis and architecture pattern selection to capture the constraints and rationale driving decision-making for future reference and audits.

Can I use ADR templates for requirement analysis and pattern selection across different projects?▼

Yes, ADR templates apply to requirement analysis, trade-off evaluation, and pattern selection across projects, providing a standard structure for recording decisions and capturing constraints.

How does frontmatter-driven entry point guide architecture decision-making?▼

A frontmatter-driven entry point enforces selective reading rules that guide architecture decision-making by structuring ADR templates to consistently capture rationale and constraints.

What are the limitations of using ADRs for software architecture documentation?▼

ADRs focus on documenting decisions and rationale rather than generating code, serving as an audit and reference tool for decision-making rather than an automated architecture enforcement mechanism.

Related Skills

Explore More Software Engineering Skills→
nguyenphpnguyenphp
41

architecture

Facilitate architectural decision-making with requirements analysis, trade-off evaluation, and ADR documentation.

Community
Advanced
klu-devklu-dev
2

continuous-learning

Extract patterns from coding sessions and save them to VS Code memory.

Community
Advanced
jagreehaljagreehal
3

system-architecture

Document architecture decisions and trade-offs using ADR patterns.

Community
Basic
rafaelminatto1rafaelminatto1

architecture

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

Community
Intermediate