Architecture Brief

Write concise executive summaries of architecture. Communicate decisions and tradeoffs to non-technical stakeholders. Use when presenting to leadership or documenting decisions.

48 stars 10 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill architecture-brief
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/communication/skills/architecture-brief ~/.claude/skills/architecture-brief

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Architecture Brief

Create concise, executive-friendly summaries of architecture decisions and tradeoffs.

## Context

You are writing architecture briefs for diverse audiences (executives, product, non-technical stakeholders). Explain decisions in business terms, not technical jargon. Emphasize impact on cost, speed, reliability.

## Domain Context

Based on effective technical communication:

- **Business Impact**: How does architecture choice affect time-to-market, cost, reliability? Quantify where possible.
- **Trade-offs**: Every architecture choice sacrifices something. Explicitly state: "We chose X over Y because Z matters more."
- **Risk Acknowledgment**: What could go wrong? Residual risks accepted. Mitigation plans for critical risks.
- **Assumptions**: What's true about our context that makes this choice right? Different context, different choice.

## Instructions

1. **One-Pager Structure**:
   - Title: "API Gateway Architecture for Microservices"
   - Problem: "Multiple services exposing APIs; no unified interface, inconsistent auth, no rate limiting"
   - Decision: "Implement API Gateway (Kong/AWS API Gateway)"
   - Rationale: "Centralizes auth, rate limiting, routing; 2-week implementation"
   - Trade-off: "Extra hop in request path (5ms latency); operational overhead of new service"
   - Success Metrics: "Consistent error responses, 99.9% uptime, < 50ms latency"
   - Risks: "Gateway becomes bottleneck (mitigation: auto-scaling, load testing)"
Read the full skill on GitHub

Details

Skill name
architecture-brief
Path
architect/communication/skills/architecture-brief/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Architecture Brief skill do?

Write concise executive summaries of architecture. Communicate decisions and tradeoffs to non-technical stakeholders. Use when presenting to leadership or documenting decisions.

How do I install the Architecture Brief skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Architecture Brief popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.