architecture

Create and evaluate architecture decision records for system design choices.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ilove323/comlan-skills --skill architecture-ilove323
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/ilove323/comlan-skills/tree/main/engineering/skills/architecture
Command: npx skills add https://github.com/ilove323/comlan-skills --skill architecture-ilove323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering teams choose between competing technical solutions and capture those decisions as clear, actionable Architecture Decision Records (ADRs), reducing ambiguity and technical drift.

Core Features & Use Cases

  • Create ADRs: Produce standardized ADR documents with background, decision, considered options, trade-off analysis, consequences, and action items.
  • Evaluate designs: Review system or component proposals (for example, Kafka vs SQS or microservice boundaries) and surface trade-offs and risks.
  • System design guidance: Provide constraints-driven recommendations for new components such as notification systems or event buses.
  • Integrations: When connected to a knowledge base or project tracker, locate previous ADRs, relate issues, and suggest implementation tasks.

Quick Start

Create an ADR comparing Kafka and SQS for our event bus that must support 10k rps, low latency, and team familiarity constraints.

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 to reduce technical drift?

Architecture decision records (ADRs) document system design choices by capturing background, enumerating alternatives with trade-offs, and listing consequences. They reduce ambiguity by providing clear, actionable records of component-level decisions.

What is the best way to compare messaging systems like Kafka and SQS for an event bus?

Evaluating messaging systems requires an architecture decision record that applies constraints like 10k rps and low latency. The review surfaces trade-offs and risks between options, recommending a specific decision with actionable implementation steps.

How do I review a microservice proposal and surface design trade-offs?

Reviewing microservice boundaries involves evaluating system proposals against constraints to identify trade-offs and risks. An architecture decision record documents the background, considered options, and consequences to standardize the design review process.

Can I use architecture decision records for designing a new notification system?

Architecture decision records support system design guidance for new components like notification systems. They provide constraints-driven recommendations by documenting background, evaluating alternatives, and listing actionable implementation steps.

What should an architecture decision record include for system design choices?

An architecture decision record should include background, considered options, trade-off analysis, a recommended decision, consequences, and action items. This standardized structure captures component-level and system-level design decisions.