Architecture

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

FeaturedInstructions onlySoftware Development Productivity & Workflow

AI-generated overview

Creates or evaluates architecture decision records (ADRs) and system design proposals with trade-off analysis.

What it does: This skill produces an Architecture Decision Record in a fixed markdown format, covering context, decision, options considered, trade-off analysis, consequences and action items. It can also evaluate an existing system design proposal or design a new component from stated requirements and constraints. Optionally it links to a knowledge base for prior ADRs and to a project tracker for related epics and implementation tasks.
When to use it: Use it when choosing between technologies such as Kafka versus SQS, documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Requirements: Instructions only; no scripts are shipped. Optional connectors to a knowledge base and a project tracker are mentioned for searching prior ADRs and linking or creating tasks.

/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

Modes

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

markdown

# 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 Items1. [ ] [Implementation step]2. [ ] [Follow-up]

# 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 Items1. [ ] [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

State constraints upfront — "We need to ship in 2 weeks" or "Must handle 10K rps" shapes the answer.
Name your options — Even if you're leaning one way, I'll give a more balanced analysis with explicit alternatives.
Include non-functional requirements — Latency, cost, team expertise, and maintenance burden matter as much as features.

Source and attribution

Source:anthropics/knowledge-work-pluginsinengineering/skills/architectureat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today

Architecture

/architecture

Usage

Modes

Output — ADR Format

If Connectors Available

Tips

Source and attribution

More from anthropics/knowledge-work-plugins

Ticket Deflector

Tax Season Organizer

Tax Prep

Smb Onboard

Smb Router

Month End Prep

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices