Verified:GitHub

architecture-decision-records

Manage the creation, documentation, and lifecycle of Architecture Decision Records.

Updated Mar 11, 2026

Search Tags:#software architecture #technical documentation #knowledge sharing #decision management #architecture decision records

Ready to run

npx skills add https://github.com/act70255/SkillsBundle --skill architecture-decision-records-act70255

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/act70255/SkillsBundle/tree/main/planning/skills/architecture-decision-records
Command: npx skills add https://github.com/act70255/SkillsBundle --skill architecture-decision-records-act70255

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of documenting significant technical decisions, ensuring clarity, traceability, and collaboration within your team.

Core Features & Use Cases

ADRs for Technical Decisions: Capture context, rationale, and consequences of technical decisions.
Documentation and Collaboration: Facilitate knowledge sharing and onboarding of new team members.
Lifecycle Management: Manage the lifecycle of ADRs from proposed to deprecated.

Quick Start

Create a new Architecture Decision Record (ADR) to document the decision to migrate user profiles from MongoDB to PostgreSQL.

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 software architecture decisions for my team?▼

You document software architecture decisions using Architecture Decision Records (ADRs) to capture the context, rationale, and consequences of technical choices. This ensures clarity, traceability, and collaboration within your software development team.

What is the best way to manage the lifecycle of technical documentation for architecture decisions?▼

Managing the lifecycle of technical documentation for architecture decisions involves tracking each record from proposed to deprecated. This lifecycle management ensures that evolving software systems maintain accurate historical context and rationale.

When do I need architecture decision records in software development?▼

You need architecture decision records when maintaining and evolving large software systems to ensure significant technical decisions are traceable. They are essential for knowledge sharing, onboarding new team members, and documenting complex migrations.

Can I use architecture decision records to document a database migration?▼

Yes, you can use architecture decision records to document a database migration by detailing the context and consequences of the move. For example, you can create an ADR to document the decision to migrate user profiles from MongoDB to PostgreSQL.

Does managing architecture decision records require any specific frameworks or dependencies?▼

Managing architecture decision records requires no specific external frameworks or dependencies. The process relies on internal scripts and references to document technical decisions and facilitate knowledge sharing within your existing software engineering workflow.