software-architect

To document software architecture trade-offs, you can generate Architecture Decision Records (ADRs) that capture the context, decision, and consequences. This Skill provides a systematic framework to elicit quality attributes, explore candidate approaches, and formalize the resulting trade-off analysis into structured ADR artifacts.

Yes, you can generate C4 model descriptions to analyze and review system architecture. This Skill supports creating these structured descriptions to visualize system context, containers, components, and code levels, facilitating architectural analysis and ensuring designs meet business goals.

You assess quality attributes during a code or PR review by evaluating code quality, identifying architectural risks, and suggesting fitness functions. This Skill provides a framework to review pull requests against architectural principles and verify adherence to specified quality attributes.

The best way to elicit quality attributes for a new microservice is using a systematic architectural framework. This Skill facilitates quality attribute elicitation and trade-off analysis, ensuring your microservice design meets scalability, security, and other business goals before implementation.

Yes, this architectural analysis framework supports generating fitness functions. It assesses code quality and adherence to architectural principles during reviews, allowing you to define and suggest fitness functions that continuously validate your system architecture against established quality attributes.

You should use ADRs instead of general software design documentation when you need to rigorously capture specific architectural decisions and their trade-offs. This Skill focuses on generating Architecture Decision Records to document the context, decision drivers, and consequences of your architectural choices.