architecture

Guide architectural decision-making with requirement analysis and Architecture Decision Records.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Andrejr82/Caculinha_BI --skill architecture-andrejr82
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/Andrejr82/Caculinha_BI/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/Andrejr82/Caculinha_BI --skill architecture-andrejr82

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making and documenting architectural decisions, ensuring that requirements are met, trade-offs are considered, and decisions are well-justified.

Core Features & Use Cases

  • Requirement Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Provides templates and methods for analyzing different architectural options.
  • ADR Documentation: Facilitates the creation of Architecture Decision Records to capture the rationale behind choices.
  • Use Case: When deciding whether to adopt a microservices architecture or a modular monolith, use this Skill to explore the pros and cons, document the decision, and outline the accepted trade-offs.

Quick Start

Use the architecture skill to help document a new decision about data storage.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record (ADR) captures the rationale behind a system design choice. You need an ADR when making significant architectural decisions to ensure trade-offs are considered and choices are well-justified for future reference.

How do I evaluate trade-offs between a microservices architecture and a modular monolith?

To evaluate architectural trade-offs between a microservices architecture and a modular monolith, use a structured decision framework to analyze project requirements, compare system design patterns, and document the accepted pros and cons of each option.

How do I document system design patterns and architectural choices for a new project?

You document architectural choices by creating Architecture Decision Records (ADRs) that outline the requirement analysis, selected system design patterns, and the clear rationale for the accepted trade-offs.

Can I use this architectural decision framework for any software engineering system design?

Yes, you can use this architectural decision framework for any software engineering system design. It provides a structured process for requirement analysis and trade-off evaluation without requiring specific platform dependencies.

What is the best way to analyze project requirements before making architectural decisions?

The best way to analyze project requirements for architectural decisions is to use a structured framework that guides you through understanding project needs and constraints before evaluating system design patterns and trade-offs.