architect

Draft ADRs and evaluate technology trade-offs across service boundaries.

17|1|Updated Feb 3, 2026

Search Tags:#architecture #scalability #adr #governance #trade-offs #system-design

Ready to run

npx skills add https://github.com/Adelie-Squad/solosquad --skill architect-adelie-squad

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Adelie-Squad/solosquad/tree/main/agents/specialists/architect
Command: npx skills add https://github.com/Adelie-Squad/solosquad --skill architect-adelie-squad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions and cross-service design often drift without a structured approach. This Skill provides a centralized framework to draft ADRs, define system boundaries, and evaluate technology trade-offs with collaboration prompts.

Core Features & Use Cases

ADR drafting and governance for system design across multiple services
Service boundary definition, data ownership delineation, and scalability considerations
Reference architecture patterns and trade-off analysis to guide technical decisions
Use Case: When evaluating whether to split a monolith into microservices, create ADRs and decision records to capture contexts, options, and consequences.

Quick Start

Draft an ADR for your upcoming service boundary change and use it to align engineering and product decisions.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I draft an ADR for splitting a monolith into microservices?▼

To draft an ADR for splitting a monolith, define service boundaries, evaluate technology trade-offs, and capture the context, options, and consequences of the decision. This structured approach ensures coherent architecture and aligns engineering with product decisions.

What is the best way to define service boundaries and data ownership across multiple teams?▼

Defining service boundaries and data ownership requires cross-service system design coordination to ensure coherent architecture. By applying structured governance and explicit gate checks, multiple teams can delineate scalability considerations and maintain clear data ownership.

When do I need formal architecture governance for system design?▼

You need formal architecture governance for system design when managing large-scale software projects that require service boundaries, technology choices, and trade-off evaluations across multiple teams. It prevents architectural drift by applying explicit gate checks and collaboration prompts.

How does trade-off analysis work for reference architecture patterns?▼

Trade-off analysis for reference architecture patterns evaluates different technology choices and system boundaries to guide technical decisions. It provides a centralized framework to compare options, assess scalability considerations, and capture the consequences within an ADR.

Can I use this for large-scale software projects requiring cross-service coordination?▼

Yes, this is explicitly designed for large-scale software projects requiring cross-service coordination. It applies to environments needing service boundary definition, technology choices, and trade-off evaluations across multiple teams to ensure a coherent architecture.