skills.rest
anavvanzin
anavvanzinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agency-software-architect

Create software architectures balancing domain modeling, architectural patterns, and ADR-driven decisions across monoliths and microservices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design software architectures that balance domain modeling, architectural patterns, and decision records to ensure scalable, maintainable systems.

Core Features & Use Cases

  • Domain modeling and bounded context identification.
  • Architectural pattern selection and trade-off analysis (modular monolith, microservices, event-driven).
  • ADR-driven decision documentation and evolution planning.

Quick Start

Create an ADR for a new service boundary that captures context, options, and rationale.

Frequently Asked Questions about agency-software-architect

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

FAQPage Schema
How do I document architectural decisions for a new service boundary?▼

To document architectural decisions, create an Architecture Decision Record (ADR) that captures the context, options, and rationale for the chosen system design. This decision documentation ensures maintainable software architecture.

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

Choosing between a modular monolith and microservices requires architectural pattern selection and trade-off analysis based on your domain modeling constraints. Evaluate bounded contexts to balance system maintainability against scalability.

How does domain-driven design help with system architecture?▼

Domain-driven design helps system architecture by identifying bounded contexts and mapping domain models. This context mapping ensures architectural patterns align with business requirements for maintainable software systems.

Can I use this approach for event-driven architecture trade-off analysis?▼

Yes, you can use this approach for event-driven architecture trade-off analysis. The architectural pattern selection process evaluates event-driven systems against alternatives to guide maintainable evolution planning.

When do I need to create an Architecture Decision Record?▼

You need to create an Architecture Decision Record when making significant architectural choices like selecting system patterns or defining service boundaries. ADRs provide context and rationale for evolution planning.

What are the limitations of microservices compared to a modular monolith?▼

The limitations of microservices compared to a modular monolith involve trade-offs in system complexity and maintainability. Trade-off analysis evaluates domain modeling needs to determine if distributed patterns are justified.

Related Skills

Explore More Software Engineering Skills→
2good4me2good4me

architecture

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

Community
Advanced
etretr
41

architecture

Translate product requirements into architecture.md and ADR-lite records.

Community
Advanced
agnaldo4jagnaldo4j
1

microservices-modular-monolith

Evaluate architectural boundaries to determine modular monolith to microservices transition paths.

Community
Advanced
microscalermicroscaler
1

System Design

Translate product requirements into system topologies, ADRs, and Mermaid diagrams.

Official
Advanced