architecture

Generate ADR documentation and recommended patterns for architectural decisions.

Updated Aug 30, 2024
One-click install
npx skills add https://github.com/jfrometa/esquizo --skill architecture-jfrometa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/jfrometa/esquizo/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/jfrometa/esquizo --skill architecture-jfrometa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making is complex and error-prone; this Skill provides an ADR-driven framework, templates, and references to guide decisions.

Core Features & Use Cases

  • ADR templates for documenting decisions and rationale
  • Guidance for requirements discovery, trade-off analysis, and pattern selection
  • Reference patterns and examples to accelerate architecture work

Quick Start

Describe the architecture decision you are facing; the skill will generate an ADR 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 document architectural decisions and trade-offs for system design?▼

To document architectural decisions, use an ADR-driven framework with templates that capture decisions, rationale, and trade-offs. This provides structured records of your system design choices and justifications for future reference.

What is an ADR and when do I need it for architecture decisions?▼

An ADR is an Architectural Decision Record that documents decisions and rationale. You need ADRs when facing complex architecture choices requiring requirements analysis and trade-off evaluation to justify pattern selection.

How do I evaluate trade-offs when choosing between system design patterns?▼

Evaluate trade-offs by applying a structured framework that analyzes requirements and compares design patterns. This generates an ADR documenting evaluated alternatives and the rationale behind the selected system design pattern.

Can I use this framework for any system design scale or specific platforms?▼

The framework applies broadly to system design across scales, focusing on pattern selection and trade-off evaluation rather than platform specifics. It provides checklists and example ADRs to guide architecture work.

What's the best way to start writing an ADR for a new architecture decision?▼

Start writing an ADR by describing the architecture decision you are facing. The framework then generates an ADR document and recommended patterns based on requirements analysis and trade-off evaluation.

What are the limitations of using ADR templates for pattern selection?▼

ADR templates provide structure but do not replace deep domain expertise in pattern selection. They guide requirements analysis and trade-off evaluation, yet architecture decisions still require manual interpretation of rationale.