Architecture Decision Records

Generate, evaluate, patch, and recheck Architecture Decision Records from requirements and diagrams.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zthanos/so-workspace --skill architecture-decision-records-zthanos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture Decision Records
Source: https://github.com/zthanos/so-workspace/tree/main/assets/templates/skills/adr
Command: npx skills add https://github.com/zthanos/so-workspace --skill architecture-decision-records-zthanos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often undocumented, inconsistently linked to requirements, objectives, and diagrams, making governance and traceability difficult.

Core Features & Use Cases

  • Generate: Create Architecture Decision Records from requirements, objectives, diagrams, and the solution outline.
  • Evaluate: Assess ADR completeness, consistency, and architectural quality against artifacts.
  • Patch & Recheck: Update ADRs and re-validate them after changes.

Quick Start

Create a new ADR by running the Generate workflow to produce docs/04_decisions/ADR-XXX.md.

Frequently Asked Questions about Architecture Decision Records

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

FAQPage Schema
How do I document architectural decisions to ensure traceability across requirements and diagrams?

You can document architectural decisions by generating Architecture Decision Records that tie requirements, objectives, and architecture diagrams together to ensure traceability and governance across your software engineering artifacts.

What is the best way to generate an Architecture Decision Record from existing solution outlines?

The best way to generate an Architecture Decision Record is to run a workflow that evaluates your solution outline, requirements, and objectives to produce a structured markdown file in your decisions directory, ensuring consistency across artifacts.

How do I update and re-validate Architecture Decision Records after making changes to the architecture?

You can update and re-validate Architecture Decision Records by applying a patch and recheck workflow that updates the ADRs and re-validates them against artifacts to ensure completeness and consistency after changes are made.

Can I assess the completeness and consistency of my existing ADRs against architectural artifacts?

Yes, you can assess ADR completeness, consistency, and architectural quality by evaluating them against your requirements, objectives, and architecture diagrams to maintain governance across your documentation.

Do I need predefined templates to govern and manage Architecture Decision Records effectively?

You need predefined templates to govern and manage Architecture Decision Records effectively, as they ensure consistency and traceability by tying ADRs to your existing artifacts and solution outline structure.