skills.rest
omeraltn
omeraltnCOMMUNITY
Explore all skills by this author →
GitHub

agency-software-architect

Design software architectures with bounded contexts, trade-off matrices, and ADR templates.

Updated Apr 11, 2026
Search Tags:#scalability#system design#microservices#adr#domain-driven design#software architecture#trade-offs
One-click install
npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-software-architect-omeraltn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-software-architect
Source: https://github.com/omeraltn/ice_cream_website_testing/tree/main/.antigravity/agency-software-architect
Command: npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-software-architect-omeraltn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams and technical leaders design maintainable, scalable, and evolution-friendly software systems while avoiding unnecessary complexity and undocumented decisions. It focuses on translating business domains into bounded contexts, choosing appropriate architectural patterns, and producing clear architectural decision records to guide future change.

Core Features & Use Cases

  • Domain Modeling & Bounded Contexts: Identify context boundaries, aggregates, and domain events to minimize coupling and preserve invariants.
  • Architecture Selection & Trade-offs: Recommend when to use modular monoliths, microservices, event-driven systems, or CQRS and document the trade-offs for each choice.
  • Decision Documentation (ADRs): Provide ADR templates and example records that capture context, options, decisions, and consequences for long-term clarity.
  • Quality-Attribute Driven Design: Advise on scalability, reliability, maintainability, and observability with patterns like circuit breakers, retries, and tracing.

Quick Start

Ask the agent to design a domain-driven architecture for an online store, listing bounded contexts, aggregate boundaries, integration patterns, a trade-off analysis, and a final ADR summarizing the decision.

Frequently Asked Questions about agency-software-architect

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

FAQPage Schema
How do I design software architecture for a complex business domain using bounded contexts?▼

Designing software architecture for complex domains involves identifying bounded contexts, aggregates, and domain events to minimize coupling and preserve invariants. This produces bounded context maps and component responsibilities that guide maintainable system evolution.

When should I choose a modular monolith versus microservices for my system design?▼

Choosing between a modular monolith and microservices depends on your scalability and reliability constraints. Trade-off analysis evaluates unnecessary complexity against independent deployment, documenting the decision with architecture selection matrices and ADR templates.

What is the best way to document architectural decisions for long-term maintainability?▼

Documenting architectural decisions is best achieved through Architecture Decision Records (ADRs) that capture context, options, decisions, and consequences. This provides long-term clarity and guides future system changes without undocumented technical debt.

How do I plan a monolith to microservices transition with event-driven systems?▼

Planning a monolith to microservices transition requires evolution planning that maps domain boundaries and integration patterns. It recommends event-driven systems or CQRS where appropriate, ensuring observability and reliability through circuit breakers and tracing.

Does quality-attribute driven design help with scalability and observability requirements?▼

Quality-attribute driven design directly addresses scalability and observability by applying patterns like circuit breakers, retries, and tracing. It ensures architecture selections satisfy reliability and maintainability requirements while minimizing unnecessary system complexity.

Related Skills

Explore More Software Engineering Skills→
2good4me2good4me

architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions in ADR format.

Community
Advanced
preedeppreedep

architecture-designer

Design scalable system architectures and document decisions with ADRs.

Community
Advanced
camilooscargbaptistacamilooscargbaptista
7

domain-modeling

Model complex business domains and define bounded contexts for scalable architectures.

Community
Intermediate
rnavarychrnavarych
14

system-design

Guide system design pattern selection for distributed systems architectures.

Community
Advanced