Architecture: Install, Source and Security | FunnelSlayer
FunnelSlayer
Book a call

Architecture

Published by anthropics in knowledge-work-plugins

No known issues6.6k installs

What this skill does

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.

Add Architecture to your agent

Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.

Install with a prompt

Paste this into a compatible coding agent:

add this skill "architecture" from https://github.com/anthropics/knowledge-work-plugins

Install with the CLI

Run this command in a controlled environment after reviewing the repository:

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill architecture

Skill instructions

/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 $ARGUMENTS

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

# 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.

Files included

  • SKILL.md

More skills