architecture

Guide architectural decision-making with requirements analysis and ADR documentation.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/OmarMira/Coontabilidad --skill architecture-omarmira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/OmarMira/Coontabilidad/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/OmarMira/Coontabilidad --skill architecture-omarmira

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 clarity, consistency, and maintainability in system design.

Core Features & Use Cases

  • Decision Framework: Guides users through evaluating options, trade-offs, and selecting appropriate architectural patterns.
  • ADR Documentation: Facilitates the creation of Architecture Decision Records to capture rationale and context.
  • Use Case: When deciding between a monolithic or microservices architecture, this Skill helps analyze requirements, weigh pros and cons, and document the final choice with clear justifications.

Quick Start

Use the architecture skill to document a decision about choosing a database technology.

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 for system design?

Architecture Decision Records (ADRs) document architectural decisions by capturing the rationale, trade-offs, and context evaluated during system design to ensure maintainability.

What is the best way to evaluate trade-offs between microservices and monolithic architecture?

Evaluating microservices versus monolithic architecture trade-offs involves analyzing project requirements, weighing pros and cons, and validating choices against your specific system constraints and goals.

How do I select appropriate design patterns for my project constraints?

Select design patterns by validating architectural choices against project constraints and goals, using a structured framework to evaluate options and ensure they fit your requirements.

When do I need to create an Architecture Decision Record?

You need an Architecture Decision Record when making significant system design choices, such as selecting a database technology, to provide a structured framework for evaluating options and ensuring clarity.

Does this architecture decision framework support requirements analysis for software engineering?

Yes, the architecture decision framework supports software engineering by guiding users through requirements analysis and trade-off evaluation before validating and documenting the final architectural patterns.