skills.rest
Icebane84
Icebane84COMMUNITY
Explore all skills by this author →
GitHub

architecture

Structure requirements, constraints, and trade-offs into ADR-style architecture decision records.

Updated Mar 24, 2026
Search Tags:#architecture#system design#adr#requirements analysis#trade-off analysis#modular monolith#pattern selection
One-click install
npx skills add https://github.com/Icebane84/Synarche_Workshop --skill architecture-icebane84
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Icebane84/Synarche_Workshop/tree/main/.agent/skills/dev/architecture
Command: npx skills add https://github.com/Icebane84/Synarche_Workshop --skill architecture-icebane84

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid weak or overcomplicated system design by turning requirements into clear architecture decisions, supported by trade-offs and ADR-style rationale.

Core Features & Use Cases

  • Requirements-to-architecture guidance: ensures decisions start from clarified requirements and constraints.
  • Trade-off and pattern selection: evaluates options (including anti-pattern risks) and selects patterns appropriate to problem scope and constraints.
  • ADR documentation structure: captures decision context, options considered, rationale, accepted trade-offs, consequences, and revisit triggers.
  • Use Case: When planning a new product’s system (e.g., choosing between modular monolith vs microservices), use this framework to document why the choice fits scale, team size, and timeline.

Quick Start

Ask the AI to produce an architecture decision record for your system design problem, explicitly covering requirements, options considered, trade-offs accepted, and consequences.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I write an architecture decision record for system design?▼

To write an architecture decision record (ADR), structure your system design requirements, constraints, and trade-off analysis into a documented rationale that captures context, options considered, consequences, and revisit triggers.

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

Choosing between a modular monolith and microservices requires evaluating trade-offs against your scale, team size, and timeline, ensuring the selected pattern fits the problem scope and deferring unnecessary complexity.

How do you perform trade-off analysis for pattern selection in system design?▼

Trade-off analysis for pattern selection evaluates architectural options against clarified requirements and constraints, identifies anti-pattern risks, and documents accepted consequences to ensure the chosen design fits the problem scope.

When do I need ADR documentation for distributed system decisions?▼

You need ADR documentation for distributed system decisions when planning early-stage product architecture, ensuring every choice satisfies validation checks by considering simpler alternatives and recording consequences.

Can I use this approach for DDD and modular monolith architecture?▼

Yes, this approach supports DDD and modular monolith architecture decisions by structuring requirements analysis and pattern selection into rationale-driven outcomes with documented trade-offs and revisit triggers.

Why should I consider simpler alternatives before committing to a distributed system?▼

Considering simpler alternatives before committing to a distributed system ensures you defer unnecessary complexity, satisfying validation checks that protect against overcomplicated system design and weak architectural decisions.

Related Skills

Explore More Software Engineering Skills→
jikimejikime
5

jikime-domain-architecture

Select architecture patterns, generate directory templates, and create Architecture Decision Records.

Community
Advanced
abdullah1854abdullah1854
1

algorithmic-art

Generate dated Markdown ADRs with Context, Decision, Consequences, Alternatives, and References.

Community
Intermediate
LLM-Dev-OpsLLM-Dev-Ops
1

V3 DDD Architecture

Decompose monolithic orchestrators into bounded contexts with Domain-Driven Design.

Official
Advanced
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic