architecture

Structure architectural decisions with trade-off analysis and ADR templates.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/darthlinuxer/dialectic-crew-ai --skill architecture-darthlinuxer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/darthlinuxer/dialectic-crew-ai/tree/main/src/mcp/skills/architecture
Command: npx skills add https://github.com/darthlinuxer/dialectic-crew-ai --skill architecture-darthlinuxer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and engineers make well-reasoned architectural decisions by structuring requirements analysis, trade-off evaluation, pattern selection, and ADR documentation to reduce costly rework and hidden risks.

Core Features & Use Cases

  • Requirements-driven analysis: Guided question hierarchy to classify projects by scale, team, timeline, domain, and constraints.
  • Trade-off documentation & ADRs: Templates and a decision framework to record options, rationale, consequences, and revisit triggers.
  • Pattern selection & anti-patterns: Decision trees for choosing data access, domain, and distributed system patterns with red-flag guidance.
  • Validation checklist: Pre-finalization checks to ensure constraints, trade-offs, and team capabilities align with chosen architecture.
  • Use Case: Generate an ADR recommending modular monolith versus microservices for a growing SaaS team, including accepted trade-offs and migration path.

Quick Start

Ask the architecture skill to analyze your project's scale, team, timeline, and constraints and produce an ADR with trade-off analysis and recommended patterns.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I write an ADR for choosing between a modular monolith and microservices?

To write an ADR for modular monolith versus microservices, analyze your project's scale, team, timeline, and constraints to produce structured trade-off documentation with recommended patterns, rationale, consequences, and migration paths.

What is the best way to evaluate system design trade-offs for a SaaS application?

Evaluating system design trade-offs for a SaaS application requires a requirements-driven decision framework that classifies constraints and applies a validation checklist to ensure chosen architecture aligns with team capabilities and compliance needs.

How do I select the right architectural patterns for distributed systems?

Selecting architectural patterns for distributed systems uses decision trees for data access, domain, and distributed system design, complete with red-flag anti-pattern guidance to validate choices against your specific constraints.

Can I use a structured decision framework for enterprise architecture validation?

Yes, you can use a structured decision framework for enterprise architecture validation by applying a pre-finalization checklist that verifies constraints, trade-offs, and team capabilities align with the chosen system design.

When do I need to document architectural decisions and trade-offs?

You need to document architectural decisions and trade-offs whenever classifying projects by scale, domain, or constraints to reduce costly rework, capture rationale, and establish revisit triggers for MVP, SaaS, or enterprise scenarios.

What are the limitations of pattern selection without requirements analysis?

Without requirements analysis, pattern selection lacks validation against scale, team, timeline, and compliance constraints, increasing hidden risks and costly rework from choosing inappropriate data access or domain patterns.