architecture

Document architectural decisions with trade-offs using ADR templates.

Updated Feb 19, 2026

Search Tags:#architecture #documentation #adr #patterns #trade-offs #software-design #decision-record

Ready to run

npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill architecture-jonnathan-ls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/jonnathan-ls/ai-context-kit/tree/main/skills/architecture
Command: npx skills add https://github.com/jonnathan-ls/ai-context-kit --skill architecture-jonnathan-ls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions often drift without a formal record of context, options, and rationale.

Core Features & Use Cases

ADR templates to document decisions with context, options, and trade-offs.
Lifecycle guidance from proposal to archival, enabling traceability and re-use.
Context & templates to support consistent patterns across projects.

Quick Start

Create an ADR for your next significant design choice using the framework and update it as the project evolves.

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 effectively?▼

Document architectural decisions using the Architecture Decision Record (ADR) format, which captures context, options, and trade-offs to provide clear rationale for technology choices and system designs.

What is an ADR and when should I use one for software design?▼

An ADR is an Architecture Decision Record used to formally document significant software-design choices, ensuring that context and rationale are preserved rather than drifting over time as projects evolve.

How do I create an ADR template for tracking technology choices?▼

Create an ADR using a structured template that tracks context, available options, and trade-offs, providing lifecycle guidance from initial proposal through to archival for consistent decision records.

Can I use ADRs for small projects or are they only for large-scale system designs?▼

ADRs are applicable to projects at any scale, supporting structured decision records for technology choices, patterns, and system designs whenever a formal record of context and rationale is needed.

What is the best way to manage the lifecycle of an architectural decision record?▼

Manage ADR lifecycles by following structured guidance from proposal to archival, allowing teams to revisit and update decisions as the project evolves while maintaining traceability and enabling re-use.

Why does architectural context drift without formal decision records?▼

Architectural context drifts because teams lack a formal record of the options and rationale behind a decision, making it difficult to trace trade-offs and maintain software-design consistency over time.