design-architecture

Create and evaluate Architecture Decision Records for cross-cutting data design decisions.

Updated Jun 20, 2026

Search Tags:#documentation #adr #governance #software-design #architecture-decisions #cross-repo #design-record

Ready to run

npx skills add https://github.com/lowmason/agent-skills --skill design-architecture-lowmason

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-architecture
Source: https://github.com/lowmason/agent-skills/tree/main/design-architecture
Command: npx skills add https://github.com/lowmason/agent-skills --skill design-architecture-lowmason

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Architecture decisions are captured as immutable records that explain why a cross-cutting choice was made, preventing re-litigation and providing an auditable trail.

Core Features & Use Cases

Authoring: create new Architecture Decision Records to document significant, hard-to-reverse architecture choices.
Evaluating: review existing ADRs to assess the rationale, alternatives, and trade-offs.
Governance: link ADRs to specs, CLAUDE.md, or architecture documentation to maintain traceability across packages.

Quick Start

Create or evaluate an Architecture Decision Record for a cross-cutting data design decision.

Frequently Asked Questions about design-architecture

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

FAQPage Schema

How do I record architecture decisions across multiple repositories?▼

Architecture Decision Records capture cross-cutting choices as immutable records using a stable template. They document context, decision, consequences, and alternatives to provide an auditable trail across multi-repo projects.

What is an ADR lifecycle for software design governance?▼

An ADR lifecycle tracks decisions through Proposed, Accepted, and Superseded states. This structured progression ensures architecture choices remain traceable and prevents re-litigation during rework or package updates.

When do I need an Architecture Decision Record for data modeling?▼

You need an Architecture Decision Record when a data modeling choice spans multiple packages, requires traceable context, and should endure across rework. ADRs explain why hard-to-reverse decisions were made to prevent future re-litigation.

How do I link architecture decisions to specs and CLAUDE.md for governance?▼

You link architecture decisions by referencing ADRs within specs, CLAUDE.md, or architecture documentation. This maintains traceability across packages and connects the immutable decision record to active project governance.

What should I document in an Architecture Decision Record for cross-repo projects?▼

You should document the context, decision, consequences, and alternatives. Using a stable ADR template ensures the rationale for cross-cutting architecture choices is captured completely for future evaluation.

Can I evaluate existing architecture decisions to assess trade-offs?▼

You can evaluate existing ADRs to assess the rationale, alternatives, and trade-offs of accepted architecture decisions. This review process leverages the structured record of context and consequences to validate past choices.