agency-software-architect

Guide software architects in designing scalable systems with domain-driven design.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda --skill agency-software-architect-bomberoxenviosdosruedas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-software-architect
Source: https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda/tree/main/.agents/workflows/agency-software-architect
Command: npx skills add https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda --skill agency-software-architect-bomberoxenviosdosruedas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software architects and developers design robust and maintainable software systems, ensuring that they align with business domains and can scale effectively.

Core Features & Use Cases

  • System Design Guidance: Provides strategies for domain modeling, architectural patterns, and trade-off analysis.
  • Architecture Decision Records (ADRs): Offers a template for documenting and tracking architectural decisions.
  • System Design Process: Offers a structured approach for discovering bounded contexts, choosing appropriate architectures, and analyzing quality attributes.
  • Communication and Collaboration: Focuses on leading with problems and constraints, using diagrams, and presenting trade-offs.
  • Use Case: Ideal for an architect working on a new project where they need to establish a scalable system with minimal future risks.

Quick Start

Run the agent and present your project challenges. The Software Architect will guide you through domain discovery and architecture selection.

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 scalable and maintainable software architecture for a new project?

To design scalable software architecture, you must model business domains, identify bounded contexts, and select appropriate architectural patterns. This approach ensures systems align with business requirements while effectively managing technical trade-offs.

What is domain-driven design and when do I need it for system design?

Domain-driven design is a strategic approach to system design that centers development on core business domains and bounded contexts. You need it when building complex systems that require strict alignment between technical implementation and business capabilities.

How do I document and track technical decision-making for architectural patterns?

You document technical decision-making by creating Architecture Decision Records (ADRs). ADRs provide a structured template for capturing architectural choices, analyzing trade-offs, and tracking quality attributes throughout the software lifecycle.

Do I need prior system architecture principles knowledge to use this design process?

Yes, this system design process requires an existing understanding of system architecture principles and patterns. It guides architects through domain discovery and architecture selection rather than teaching foundational software architecture concepts.

What is the best way to analyze quality attributes and trade-offs during system design?

The best way to analyze quality attributes during system design is through a structured trade-off analysis process. This involves evaluating architectural patterns against specific quality attributes and leading with documented problem constraints.

When should I not use domain-driven design for software architecture?

Domain-driven design may be unnecessary for simple, single-purpose applications lacking complex business logic. If your project does not require strict alignment between bounded contexts and business domains, simpler architectural patterns are more appropriate.