skills.rest
Gami19
Gami19COMMUNITY
Explore all skills by this author →
GitHub

software-architecture

Guide architecture style selection, -ilities analysis, and ADR generation.

Updated Apr 8, 2026
Search Tags:#architecture#adr#trade-offs#system-architecture#risk-analysis#design-decision
One-click install
npx skills add https://github.com/Gami19/rd-strands-agents --skill software-architecture-gami19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/Gami19/rd-strands-agents/tree/main/strands-py/backend/agent/skills/pr/software-architecture
Command: npx skills add https://github.com/Gami19/rd-strands-agents --skill software-architecture-gami19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework to help engineers design, evaluate, and document software architectures, guiding style selection, -ilities analysis, ADR generation, and risk-aware trade-off documentation.

Core Features & Use Cases

  • Guides selection among architecture styles (monolith, microservices, event-driven, etc.) based on quantified -ilities and business goals.
  • Produces Architecture Decision Records (ADR) and structured trade-off analyses to support governance and traceability.
  • Supports risk assessment and fitness-function planning to ensure architectures meet reliability, security, and performance targets.

Quick Start

Provide an initial ADR and a prioritized trade-off plan by feeding your business goals into the architecture workflow.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I document trade-offs for a software architecture decision?▼

To document trade-offs for a software architecture decision, you generate an Architecture Decision Record (ADR) that captures design choices, quantifies architecture characteristics, and traces governance impacts. This provides structured trade-off analysis and traceability for evolving systems.

When do I need to perform architecture trade-off analysis?▼

You need architecture trade-off analysis when evaluating monolith-to-microservice transitions, conducting architecture reviews, or planning system evolution. It quantifies -ilities like reliability and performance against business goals to guide design decisions and risk assessment.

What is the best way to choose between microservices and monolith architectures?▼

The best way to choose between microservices and monolith architectures is by performing a quantified -ilities analysis. This evaluates architecture styles against prioritized business goals to produce a structured trade-off plan for your specific system context.

Can I generate an ADR from my business goals?▼

Yes, you can generate an Architecture Decision Record (ADR) directly from your business goals. Feeding prioritized business goals into the architecture workflow produces an initial ADR alongside a structured trade-off plan for design decisions.

How do I assess risks in an evolving system architecture?▼

To assess risks in an evolving system architecture, you perform risk-aware trade-off documentation and fitness-function planning. This ensures the architecture meets reliability, security, and performance targets during governance workflows.

Related Skills

Explore More Design & Creative Skills→
samura-devsamura-dev

product-manager

Structure product ideas into PRDs, architecture documents, and roadmaps.

Community
Advanced
buiphucminhtambuiphucminhtam
47

solution-architect

Select architecture patterns and generate ADRs with scaffolded project structure.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

advisor

Compare .NET architecture patterns and recommend the best fit.

Community
Advanced
lehuuhau1231lehuuhau1231

architecture

Guide architectural decisions through requirements analysis, trade-off evaluation, and ADR documentation.

Community
Advanced