skills.rest
cy-wali
cy-waliCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Generate Architecture Decision Records documenting technology decisions with trade-offs.

1|Updated Mar 19, 2026
Search Tags:#architecture#adr#trade-offs#system-design#design-review#technology-selection#decision-record
One-click install
npx skills add https://github.com/cy-wali/knowledge --skill architecture-cy-wali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/cy-wali/knowledge/tree/main/engineering/skills/architecture
Command: npx skills add https://github.com/cy-wali/knowledge --skill architecture-cy-wali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are high-stakes, time-consuming, and often opaque. This Skill helps teams capture the rationale behind technology choices, trade-offs considered, and the intended consequences, ensuring consistency and future maintainability.

Core Features & Use Cases

  • Create and evaluate Architecture Decision Records (ADRs) to document decisions, alternatives, and consequences.
  • Facilitate design reviews, stakeholder alignment, and knowledge transfer across teams.
  • Use cases include selecting between Kafka vs SQS, evaluating system designs, and documenting constraints and decisions for future audits.

Quick Start

Create an ADR outline for your current design decision and document the main trade-offs and actions.

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 and trade-offs for system design reviews?▼

Create an ADR outline to structure your technology selection by documenting the main trade-offs and action items. This format aligns stakeholders during design reviews by making the decision context, alternatives, and consequences explicit for future knowledge transfer.

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

An ADR is a structured document capturing technology decisions, alternatives, and consequences. You need it during technology selection or system design reviews to prevent opaque choices, align stakeholders, and ensure constraints are documented for future audits.

How do I evaluate technology selection trade-offs like Kafka vs SQS?▼

Evaluate technology trade-offs by structuring an ADR that weighs alternatives like Kafka vs SQS against intended consequences. Documenting the decision context and options ensures stakeholder alignment and captures constraints for future audits.

Can I use ADRs to facilitate architecture collaboration across teams?▼

Yes, ADRs facilitate architecture collaboration by providing a shared structured format for decision context, options, and trade-offs. This enables stakeholder alignment and knowledge transfer across teams during system design reviews and technology selection.

What should an ADR outline include for technology selection?▼

An ADR outline for technology selection should include the decision context, evaluated options, trade-offs, and action items. Capturing these elements ensures architecture choices are transparent, stakeholder alignment is achieved, and constraints are documented for future audits.

Related Skills

Explore More Software Engineering Skills→
danilomartinellidanilomartinelli
1

architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions in ADRs.

Community
Intermediate
edwardmonteiroedwardmonteiro

delivery.design_review

Generate structured agendas and consolidate themed feedback for cross-functional design reviews.

Community
Basic
Pixel-Process-UGPixel-Process-UG
1

senior-architect

Guide system design, ADR creation, and scalability planning.

Official
Advanced
hjung3113hjung3113

ADR Format

Create and manage architectural decision records in markdown files.

Community
Basic