skills.rest
selfagency
selfagencyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decision

Evaluate architecture choices and generate ADR templates with alternatives and consequences.

Updated Mar 11, 2026
Search Tags:#architecture#refactoring#design patterns#adr#technical debt#trade-offs#quality attributes
One-click install
npx skills add https://github.com/selfagency/agentsy --skill architecture-decision-selfagency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/architecture-decision
Command: npx skills add https://github.com/selfagency/agentsy --skill architecture-decision-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically evaluate architectural choices and document clear decision trade-offs so you can reduce technical debt and improve maintainability over time.

Core Features & Use Cases

  • Framework-based evaluation: Uses a trade-off triangle (simplicity, flexibility, performance) plus quality attributes (performance, scalability, reliability, maintainability) to ground decisions in context.
  • Decision documentation: Produces ready-to-use ADR structures and refactoring pattern guidance to capture rationale and consequences.
  • Technical debt management: Classifies debt, defines metrics, and provides anti-pattern remedies to prevent recurring architectural failures.

Quick Start

Use architecture-decision when you’re deciding between two approaches and need an ADR-style write-up that explains context, rationale, and consequences.

Frequently Asked Questions about architecture-decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an ADR for choosing between two architectural patterns?▼

An ADR for architectural patterns documents context, alternatives, and consequences. This Skill generates ready-to-use ADR templates that map trade-offs against quality attributes like scalability and maintainability.

What is the best way to evaluate architecture trade-offs and reduce technical debt?▼

Evaluating architecture trade-offs to reduce technical debt requires grounding decisions in context. This Skill uses a trade-off triangle of simplicity, flexibility, and performance paired with quality attributes to prevent poorly justified choices.

How do I classify technical debt when doing a system refactoring?▼

Classifying technical debt during system refactoring involves defining metrics and identifying anti-patterns. This Skill provides remedies for recurring architectural failures to classify debt and improve long-term maintainability.

When do I need a formal architecture decision process for software design?▼

You need a formal architecture decision process when selecting design patterns or comparing technology alternatives. It ensures systematic evaluation to prevent accumulated technical debt and poorly justified choices in software engineering.

Can I map quality attributes to specific software refactoring patterns?▼

Yes, you can map quality attributes to software refactoring patterns. This Skill structures trade-offs by mapping attributes like performance, scalability, and reliability to context, generating explicit refactoring pattern guidance.

Related Skills

Explore More Software Engineering Skills→
EnigmaWUEnigmaWU
1

apply-attribute-driven-design

Execute the Attribute-Driven Design 3.0 methodology for architectural designs.

Community
Advanced
DengNaichenDengNaichen
34

axiom-audit-swiftui-architecture

Analyze SwiftUI project architecture to detect anti-patterns and testability issues.

Community
Advanced
cvillamarp-lgtmcvillamarp-lgtm

managing-tech-debt

Identify and quantify technical debt across code and architecture.

Community
Advanced
AIMFllysAIMFllys
3

architecture

Convert requirements into justified architecture decisions with ADR documentation.

Community
Intermediate