architecture

Document architecture decisions using ADR templates and trade-off checklists.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bcassiano/MariIA --skill architecture-bcassiano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/bcassiano/MariIA/tree/main/ag_kit_2/.agent/skills/architecture
Command: npx skills add https://github.com/bcassiano/MariIA --skill architecture-bcassiano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decision-making is often ad hoc; this framework provides a structured approach to capture context, options, and rationale, ensuring decisions are traceable and repeatable across projects.

Core Features & Use Cases

  • ADR templates and a standardized decision framework for documenting rationale
  • Context discovery prompts, trade-off analysis, and ADR templates to guide decisions
  • Use Cases: MVPs to enterprise systems requiring clear governance and documentation

Quick Start

Create an ADR for your architectural decision using the ADR template and document the context, options, and rationale.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architecture decisions to ensure they are traceable across projects?

To document architecture decisions traceably, use an Architecture Decision Record (ADR) template to capture context, evaluate trade-offs, and record rationale, ensuring choices are repeatable across software projects from MVPs to enterprise systems.

What is the best way to evaluate trade-offs when making software architecture choices?

Evaluating architecture trade-offs requires a structured framework that applies context discovery prompts and trade-off checklists, guiding you through requirements analysis to document the rationale behind each option.

How do I write an ADR for an MVP architecture without overcomplicating the process?

Writing an ADR for an MVP involves using a standardized template to quickly document context, options, and rationale, applying the framework to capture essential decisions without creating unnecessary governance overhead.

When do I need a formal architecture framework instead of ad hoc decision making?

You need a formal architecture framework when decisions must be traceable and repeatable, particularly for enterprise systems requiring clear governance, or when teams must understand the context and rationale behind past choices.

Can I use ADR templates for requirements analysis in enterprise software projects?

Yes, you can use ADR templates for requirements analysis in enterprise software projects, as the framework supports context discovery and trade-off evaluation to guide decision making and ensure clear governance documentation.