Architecture Decision

When you need to choose between a monolith and microservices, pick a database strategy, or document why you went with option B over option A, this gives you frameworks instead of leaving you to reinvent the wheel. It centers on ADRs with a solid template, includes a trade-off triangle for reasoning through simplicity versus flexibility versus performance, and provides context-pattern mappings for team size and scale. The anti-patterns section is honest about distributed monoliths and golden hammers. Best used alongside system-design when you need the full treatment, but stands alone well for evaluating specific architectural choices without getting lost in implementation details.

skills.sh installs: 500
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill architecture-decision --agent claude-code

Installs into .claude/skills of the current project.

Files

Architecture Decision

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns for context. Provides frameworks for pattern selection, ADR creation, and technical debt management.

When to Use This Skill

Use this skill when:

Making technology choices
Evaluating architectural patterns
Creating Architecture Decision Records
Assessing technical debt
Comparing design alternatives

Do NOT use this skill when:

Writing implementation code
Working on requirements (use requirements-analysis)
Doing full system design (use system-design)

Core Principle

Context drives decisions. No pattern is universally good or bad. The best architecture is not the most elegant—it's the one that best serves its purpose while remaining maintainable and evolvable.