skills.rest
andebet07-oss
andebet07-ossCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Document architecture decisions as ADRs with rationale and trade-offs.

Updated Apr 3, 2026
Search Tags:#architecture#documentation#adr#trade-offs#system-design#design-decision
One-click install
npx skills add https://github.com/andebet07-oss/MemoriaShare_C --skill architecture-andebet07-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/andebet07-oss/MemoriaShare_C/tree/main/skills/skills-main/.claude-plugin/plugin_01GC5sHmfRpUwySPemYHW7n5/skills/architecture
Command: npx skills add https://github.com/andebet07-oss/MemoriaShare_C --skill architecture-andebet07-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are hard to track across teams, leading to inconsistent designs and duplicated effort.

Core Features & Use Cases

  • Create an Architecture Decision Record (ADR) to document context, options, trade-offs, and consequences.
  • Evaluate design proposals and compare alternative technologies or architectures.
  • Systematically review requirements and constraints to inform decisions and obtain sign-off.

Quick Start

Create an ADR for choosing Kafka vs SQS, capturing context, options, trade-offs, and consequences.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents context, options, trade-offs, and consequences for system design choices. You need an ADR to track technology decisions across teams, preventing inconsistent designs and duplicated effort.

How do I document system design trade-offs for technology choices?▼

Document system design trade-offs by creating an ADR that systematically captures context, evaluates options, and records consequences. This structured format ensures technology choices and component-level decisions are fully traceable.

Can I use this to compare alternative technologies like Kafka vs SQS?▼

Yes, you can compare alternative technologies like Kafka vs SQS by applying an ADR. It systematically reviews requirements and constraints to evaluate design proposals, capturing the specific trade-offs and consequences of each option.

What format does an Architecture Decision Record need to follow?▼

An Architecture Decision Record needs to follow a structured format including title, status, date, deciders, context, decision, options, trade-offs, consequences, and action items to accurately capture rationale and obtain sign-off.

How do I evaluate design proposals and get sign-off across teams?▼

Evaluate design proposals by systematically reviewing requirements and constraints within an ADR. Documenting the context, options, and trade-offs clarifies the rationale behind technology choices, facilitating informed sign-off from deciders.

Related Skills

Explore More Software Engineering Skills→
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic
ngochuy13ngochuy13

architecture

Create and evaluate Architecture Decision Records in markdown structure.

Community
Basic
diriendirien
19

architecture-designer

Design high-level system architectures and document decisions with Mermaid diagrams and ADRs.

Community
Advanced
SergeiGolosSergeiGolos
1

architecture

Guide architectural decisions through requirements analysis, trade-off evaluation, and ADR documentation.

Community
Intermediate