architecture

Document architectural decisions with ADR templates capturing context, decision, and consequences.

Updated Sep 25, 2025

Search Tags:#architecture #adr #governance #trade-offs #rationale #decision-record

Ready to run

npx skills add https://github.com/iyaki/opencode-base-template --skill architecture-iyaki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/iyaki/opencode-base-template/tree/main/.agents/skills/architecture
Command: npx skills add https://github.com/iyaki/opencode-base-template --skill architecture-iyaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural teams often struggle to preserve rationale and maintain a single source of truth for why design decisions were made. This skill provides a structured framework to analyze requirements, document decisions as ADRs, and track trade-offs across projects.

Core Features & Use Cases

ADR templates and lightweight decision records to capture context, decision, and consequences
Trade-off analysis, risk and constraint capture, and governance of architecture choices
Reuse and reference of ADRs across multiple projects to align teams and reduce rework

Quick Start

Create your first ADR document describing the context, decision, and consequences to kick off your architecture decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema

What is an ADR and how does it help document architectural decisions?▼

An Architecture Decision Record captures context, decisions, and consequences to preserve rationale. It enables traceable trade-offs and maintains a single source of truth for why design choices were made across projects.

How do I write an ADR to capture trade-offs and constraints?▼

To write an ADR, use a structured template to document context, requirements analysis, the decision, and consequences. This lightweight record captures trade-offs, risks, and constraints to align teams and reduce rework.

When do I need an ADR framework for software architecture governance?▼

You need an ADR framework when architectural teams struggle to preserve rationale and require a single source of truth. It enforces a structured workflow to govern architecture choices and track decisions across multiple projects.

Can I reuse ADRs across multiple projects to align architecture choices?▼

Yes, you can reuse and reference ADRs across multiple projects. This practice aligns teams, reduces rework, and ensures architectural governance by maintaining consistent trade-off evaluation and rationale documentation.

What is the best way to evaluate trade-offs for architectural decisions?▼

The best way to evaluate trade-offs is through structured requirements analysis within an ADR workflow. This captures constraints and risks, documenting the decision and its consequences to enable traceable architectural choices.