$ loading_
Create or review ADRs to compare technologies and document design trade-offs.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "architecture" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/engineering/skills/architecture/SKILL.md 2. Save it as ~/.claude/skills/architecture/SKILL.md 3. Reload skills and tell me it's ready
Create an ADR for choosing between Kafka and AWS SQS. Context: we need to support 50k events per second, multi-region disaster recovery, limited operations capacity, and lower infrastructure complexity. Include the decision, alternatives, trade-offs, risks, consequences, and final recommendation.
A well-structured ADR comparing Kafka and SQS with a recommendation for this scenario.
Review this system design proposal: the order service will be split into a synchronous checkout API, asynchronous inventory deduction, and event-driven notifications. Identify risks in scalability, reliability, failure recovery, observability, and security, and list the key decisions that should be documented in an ADR.
A design review with key risks, improvement suggestions, and a list of decisions to capture in an ADR.
Design an audit logging service from these requirements and produce an ADR draft: multi-tenant support, at least 3 years of retention, high write throughput, query latency under 2 seconds, compliance auditing, and cloud deployment. Explain the architecture, technology choices, data storage strategy, scaling approach, and known limitations.
An implementation-oriented ADR draft covering component architecture, technical decisions, constraints, and consequences.
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.
/architecture $ARGUMENTS
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.
# 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 ~~knowledge base is connected:
If ~~project tracker is connected:
Research prospects and draft personalized outreach emails with stronger relevance and response potential.
Prepare accurate journal entries with debits, credits, and audit-ready support.
Consolidate vendor agreement status, gaps, and key deadlines across connected systems.
Decide when Zoom MCP fits and create a safe Claude setup plan.
Process Zoom real-time media, chat, transcripts, and contact-center voice streams.
Embed Zoom meetings deeply into native Windows desktop applications with C++.
Create and maintain ADRs with checks, references, and planning support.
Create, manage, diagram, and export ADRs directly from AI conversations.
Document agent decisions and pass structured context during agent handoffs.
Compare documentation claims against current source tree facts to detect architecture drift.
Automatically save and restore AI sessions to preserve architecture context and decisions.
Review system designs with a seven-step method to surface risks and improvements.