architecture

Document architecture decisions with context, options, and trade-offs in ADRs.

34|29|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/adelpro/open-tarteel --skill architecture-adelpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/adelpro/open-tarteel/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/adelpro/open-tarteel --skill architecture-adelpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making is often undocumented and poorly aligned; this Skill provides a structured framework to capture context, alternatives, rationale, and ADRs to guide design choices.

Core Features & Use Cases

  • ADR templates and decision records to capture rationale across projects
  • Context gathering, option evaluation, and outcome recording for traceability
  • Scalable guidance from solo projects to large organizations

Quick Start

Draft an ADR for your next architecture decision and document context, options, and consequences in a concise, templated format.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architecture trade-offs and design decisions for a software project?

You document architecture trade-offs by capturing context, evaluated options, and consequences using structured Architecture Decision Records. This provides traceability for design choices across software projects.

What is an ADR and when do I need it for architecture decision-making?

An ADR is an Architecture Decision Record that captures context, alternatives, and rationale. You need ADRs when architectural decision-making is undocumented or poorly aligned within your team.

How do I write an ADR that captures context, options, and consequences?

Write an ADR using a templated format to explicitly document context, options, decisions, and consequences. This ensures consistent architecture decision records across your projects.

Can I use ADR documentation for both solo projects and large organizations?

Yes, ADR documentation provides scalable guidance for architecture decision-making. It works effectively for both solo projects and large organizations to maintain decision traceability.

What's the best way to evaluate architecture options and record the rationale?

The best way to evaluate architecture options is to use a structured framework for trade-off evaluation, documenting the selected decision and its consequences in a concise ADR format.