skills.rest
anthropics
anthropicsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

architecture

Create and evaluate Architecture Decision Records for system design choices.

23.4k|2.8k|Updated Jan 23, 2026
Search Tags:#design#architecture#decision making#documentation#system design#adr
One-click install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill architecture-anthropics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/engineering/skills/architecture
Command: npx skills add https://github.com/anthropics/knowledge-work-plugins --skill architecture-anthropics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams make better technical decisions by providing a structured way to document design choices, evaluate alternatives, and ensure clarity on system architecture.

Core Features & Use Cases

  • Create Architecture Decision Records (ADRs): Document significant design decisions, including context, options considered, and consequences.
  • Evaluate System Designs: Review and provide feedback on proposed system architectures or components.
  • Use Case: When deciding whether to use Kafka or SQS for an event bus, use this Skill to generate an ADR that outlines the pros and cons of each option based on defined constraints.

Quick Start

Use the architecture skill to create an ADR for choosing between Kafka or SQS for our event bus.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document system design decisions and trade-offs for technical choices?▼

You document system design decisions by creating Architecture Decision Records that capture context, options considered, and consequences. This provides a structured way to evaluate alternatives and ensure clarity on architectural choices.

What is an ADR and when do I need one for system architecture?▼

An Architecture Decision Record (ADR) is a document logging significant design choices, including context, alternatives, and consequences. You need one when making technical decisions like choosing between Kafka or SQS for an event bus.

How do I evaluate proposed system architectures and component designs?▼

You evaluate system architectures by reviewing proposed designs against defined requirements and constraints. This process enables feedback on system design proposals and the design of new components based on technical trade-offs.

What's the best way to compare infrastructure options like Kafka or SQS for an event bus?▼

The best way to compare infrastructure options is generating an ADR that outlines the pros and cons of each choice based on defined constraints. This ensures technical decision-making processes document context, trade-offs, and consequences.

Can I use this to review existing system design proposals and provide feedback?▼

Yes, you can review existing system design proposals and provide feedback. The architecture evaluation process assesses proposed system architectures or components based on specific requirements and constraints.

Related Skills

Explore More Software Engineering Skills→
jabrenajabrena
423

030-architecture-adr-general

Generate Architecture Decision Records for Java projects through interactive conversation.

Community
Advanced
Keiji-MiyakeKeiji-Miyake

architect

Convert ambiguous project ideas into SPEC.md, DESIGN.md, and Mermaid diagrams.

Community
Intermediate
diegocanepadiegocanepa

swe-architect

Analyze software requirements and generate architecture documentation with Mermaid diagrams.

Community
Intermediate
senior-sigansenior-sigan

architecture-decision-records

Capture architectural decisions as structured ADR documents with context and rationale.

Community
Advanced