Architecture
Skill ActiveCreate 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.
To streamline the process of documenting and evaluating architectural decisions by providing structured templates and facilitating trade-off analysis.
Features
- Create Architecture Decision Records (ADRs)
- Evaluate system design proposals
- Design new system components
- Provide structured ADR output format
- Analyze technology trade-offs
Use Cases
- Choosing between technologies for an event bus (e.g., Kafka vs SQS)
- Documenting a significant design decision with its trade-offs
- Reviewing a proposed system architecture
- Designing a new component based on requirements and constraints
Non-Goals
- Detailed implementation of the chosen architecture
- Replacing a full project management tool
- Providing low-level code generation
Trust
- warning:Issues AttentionIn the last 90 days, 29 issues were opened and 4 were closed. The closure rate is approximately 12%, indicating slow attention to open issues.
Installation
First, add the marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install engineering@knowledge-work-pluginsQuality Score
Trust Signals
Similar Extensions
Pathfinder
100Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Architecture Decision Records
99Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
System Design
99Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
Understand
100Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
Cloud Architect
100Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.