Architecture
- 5k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
architecture is an agent skill for creating ADRs and evaluating system designs with explicit option trade-off analysis.
About
The architecture skill creates Architecture Decision Records or evaluates system designs from the knowledge-work-plugins collection. Modes include Create an ADR for technology choices like Kafka versus SQS, Evaluate a design such as reviewing a microservices proposal, and System design for new components from requirements and constraints. Output follows ADR format with status, date, deciders, context, decision, options considered with complexity cost scalability and team familiarity tables, trade-off analysis, consequences, and action items. It references the system-design skill for detailed requirements gathering, scalability analysis, and trade-off frameworks. When connectors are available, it searches knowledge bases for prior ADRs and links project tracker epics. Tips urge stating constraints upfront like ship timelines or throughput targets, naming explicit alternatives for balanced analysis, and including non-functional requirements such as latency, cost, expertise, and maintenance burden alongside functional needs.
- Produces ADR format with status, context, decision, options tables, and consequences.
- Supports create ADR, evaluate design, and system design modes from requirements.
- Options tables score complexity, cost, scalability, and team familiarity per alternative.
- References system-design skill for requirements gathering and scalability frameworks.
- Tips require upfront constraints, named alternatives, and non-functional requirement coverage.
Architecture by the numbers
- 5,017 all-time installs (skills.sh)
- +240 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #111 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
architecture capabilities & compatibility
- Capabilities
- adr document generation · multi option trade off comparison tables · system design evaluation mode · consequences and action item listing · connector aware prior adr search
- Works with
- jira · confluence
- Use cases
- planning · research · api development
What architecture says it does
Create an Architecture Decision Record (ADR) or evaluate a system design.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
How do I document a technology decision or evaluate a system design with balanced trade-offs?
Create or evaluate Architecture Decision Records comparing technology options with trade-off tables, consequences, and action items.
Who is it for?
Tech leads choosing between technologies or reviewing architecture proposals before implementation.
Skip if: Skip when you need implementation code; this skill produces decision records not application code.
When should I use this skill?
User chooses between technologies, requests an ADR, reviews a system design, or designs a new component.
What you get
Structured ADR or design evaluation with named options, trade-off tables, consequences, and action items.
- Architecture Decision Record
- Trade-off analysis tables
- Implementation action items
By the numbers
- Three architecture skill modes
- Options table with four dimensions
- ADR status lifecycle documented
Files
/architecture
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Create an Architecture Decision Record (ADR) or evaluate a system design.
Usage
/architecture $ARGUMENTSModes
Create an ADR: "Should we use Kafka or SQS for our event bus?" Evaluate a design: "Review this microservices proposal" System design: "Design the notification system for our app"
See the system-design skill for detailed frameworks on requirements gathering, scalability analysis, and trade-off evaluation.
Output — ADR Format
# ADR-[number]: [Title]
**Status:** Proposed | Accepted | Deprecated | Superseded
**Date:** [Date]
**Deciders:** [Who needs to sign off]
## Context
[What is the situation? What forces are at play?]
## Decision
[What is the change we're proposing?]
## Options Considered
### Option A: [Name]
| Dimension | Assessment |
|-----------|------------|
| Complexity | [Low/Med/High] |
| Cost | [Assessment] |
| Scalability | [Assessment] |
| Team familiarity | [Assessment] |
**Pros:** [List]
**Cons:** [List]
### Option B: [Name]
[Same format]
## Trade-off Analysis
[Key trade-offs between options with clear reasoning]
## Consequences
- [What becomes easier]
- [What becomes harder]
- [What we'll need to revisit]
## Action Items
1. [ ] [Implementation step]
2. [ ] [Follow-up]If Connectors Available
If ~~knowledge base is connected:
- Search for prior ADRs and design docs
- Find relevant technical context
If ~~project tracker is connected:
- Link to related epics and tickets
- Create implementation tasks
Tips
1. State constraints upfront — "We need to ship in 2 weeks" or "Must handle 10K rps" shapes the answer. 2. Name your options — Even if you're leaning one way, I'll give a more balanced analysis with explicit alternatives. 3. Include non-functional requirements — Latency, cost, team expertise, and maintenance burden matter as much as features.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
architecture is an agent skill for creating ADRs and evaluating system designs with explicit option trade-off analysis, not a generic alternative.
FAQ
Who is architecture for?
Developers and tech leads documenting architecture decisions with explicit option comparisons.
When should I use architecture?
When evaluating Kafka vs SQS, reviewing microservices proposals, or writing ADRs with trade-offs.
Is architecture safe to install?
Review the Security Audits panel on this page before installing in production.