
Architecture Decision Framework
FreeStreamline your architectural decision-making process.
Free · Opens the source repo
What Architecture Decision Framework does
The Architecture Decision Framework is designed to assist developers and architects in navigating the complexities of system design through structured decision-making. It emphasizes the importance of requirements analysis and trade-off evaluation, ensuring that every architectural decision is well-documented and justified. By utilizing this framework, teams can enhance their understanding of project requirements and constraints, leading to more informed and effective architecture choices.
The framework is organized into several key components, each serving a specific purpose in the architectural process. The context-discovery.md file provides essential questions and project classification guidelines to kickstart the architecture design phase. The trade-off-analysis.md file includes templates and frameworks for documenting decisions, enabling teams to evaluate the pros and cons of various architectural options thoroughly. Additionally, the pattern-selection.md file aids in choosing appropriate design patterns and avoiding common anti-patterns, while the examples.md file offers reference implementations for different project types, such as MVPs and SaaS applications.
This skill is particularly beneficial for teams engaged in software development who need a systematic approach to making architectural decisions. By following the guidelines and utilizing the provided resources, teams can ensure that their architecture aligns with both project goals and best practices. The framework encourages simplicity in design, advocating for the addition of complexity only when necessary, which can help prevent over-engineering and maintain project agility.
In summary, the Architecture Decision Framework is a valuable tool for any development team looking to improve their architectural decision-making process. It provides a structured approach to requirements analysis, trade-off evaluation, and documentation, which can lead to better project outcomes and more sustainable system designs.
When to use it
Use this skill when you are in the early stages of architecture design or when you need to document architectural decisions systematically.
When not to use it
This skill is not suitable for tasks that require environment-specific validation or testing, nor should it be used as a substitute for expert review.
What you can build with it
Starting a New Project
Utilize the context-discovery.md file to classify your project and outline initial requirements.
Documenting Architectural Decisions
Refer to the trade-off-analysis.md file to create structured ADRs for significant architectural choices.
Choosing Design Patterns
Use the pattern-selection.md file to navigate decision trees and avoid common anti-patterns in your architecture.
How to install Architecture Decision Framework
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/architecture --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33Architecture Decision Framework
"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
🎯 Selective Reading Rule
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
context-discovery.md | Questions to ask, project classification | Starting architecture design |
trade-off-analysis.md | ADR templates, trade-off framework | Documenting decisions |
pattern-selection.md | Decision trees, anti-patterns | Choosing patterns |
examples.md | MVP, SaaS, Enterprise examples | Reference implementations |
patterns-reference.md | Quick lookup for patterns | Pattern comparison |
🔗 Related Skills
| Skill | Use For |
|---|---|
@[skills/database-design] | Database schema design |
@[skills/api-patterns] | API design patterns |
@[skills/deployment-procedures] | Deployment architecture |
Core Principle
"Simplicity is the ultimate sophistication."
- Start simple
- Add complexity ONLY when proven necessary
- You can always add patterns later
- Removing complexity is MUCH harder than adding it
Validation Checklist
Before finalizing architecture:
- Requirements clearly understood
- Constraints identified
- Each decision has trade-off analysis
- Simpler alternatives considered
- ADRs written for significant decisions
- Team expertise matches chosen patterns
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Frequently asked questions about Architecture Decision Framework
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
