solution-architecture

Shape solution architecture for cross-cutting enterprise capabilities across systems and constraints.

Updated Apr 25, 2026

Search Tags:#architecture #security #integration #observability #decision-making #data-ownership

Ready to run

npx skills add https://github.com/Tiepbm/software-engineering-agent --skill solution-architecture-tiepbm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solution-architecture
Source: https://github.com/Tiepbm/software-engineering-agent/tree/main/skills/solution-architecture
Command: npx skills add https://github.com/Tiepbm/software-engineering-agent --skill solution-architecture-tiepbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs pragmatic solution architecture across application, integration, data, delivery, team ownership, cost, and operations while controlling complexity and trade-offs.

Core Features & Use Cases

Define business capabilities, system context, ownership boundaries, and integration contracts.
Compare options across monolith, modular monolith, microservices, managed services, and vendor products against constraints.
Produce decision-ready architecture artifacts and ADRs to support auditability, ownership, and operability.

Quick Start

Build a walking skeleton that exercises authentication, a critical workflow, persistence, and observability to establish a working baseline.

Frequently Asked Questions about solution-architecture

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

FAQPage Schema

How do I choose between a monolith, modular monolith, and microservices for enterprise architecture?▼

Choosing between monolith, modular monolith, microservices, and managed services requires comparing options against cross-cutting enterprise capabilities, data boundaries, and regulatory constraints. This produces decision-ready architecture artifacts evaluating trade-offs and complexity.

What is the best way to document architecture decisions for auditability?▼

Documenting architecture decisions for auditability involves creating Architecture Decision Records (ADRs) that enforce integration contracts, data ownership, and security considerations. This yields decision-ready artifacts supporting operability and ownership tracking.

How do I define integration contracts and data ownership across multiple teams?▼

Defining integration contracts and data ownership across multiple teams and vendors is achieved by mapping system contexts and business capabilities. This establishes clear boundaries and controls complexity across regulatory constraints.

Can I use this approach for capabilities spanning multiple vendors and regulatory constraints?▼

Yes, this approach applies directly to capabilities spanning multiple systems, teams, vendors, and regulatory constraints. It shapes pragmatic solution architecture across application, integration, data, delivery, and operations.

How do I start building a working baseline for solution architecture?▼

Start building a working baseline by constructing a walking skeleton that exercises authentication, a critical workflow, persistence, and observability. This establishes a functional foundation for subsequent delivery sequencing.

What are the limitations of choosing microservices over a modular monolith?▼

Choosing microservices over a modular monolith introduces trade-offs in integration complexity, team ownership boundaries, and cost considerations. Evaluating these limitations against enterprise constraints prevents uncontrolled operational complexity.