skills.rest
Dexploarer
DexploarerCOMMUNITY
Explore all skills by this author →
Website𝕏@dEXploarerGitHub

architecture-decision-recorder

Create and manage Architecture Decision Records with structured templates and versioned storage.

7|2|Updated Nov 9, 2025
Search Tags:#architecture#documentation#software design#technical debt#ADR#rationale#decision records
One-click install
npx skills add https://github.com/Dexploarer/hyper-forge --skill architecture-decision-recorder-dexploarer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-recorder
Source: https://github.com/Dexploarer/hyper-forge/tree/main/.claude/skills/architecture-decision-recorder
Command: npx skills add https://github.com/Dexploarer/hyper-forge --skill architecture-decision-recorder-dexploarer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically documents architectural decisions, their rationale, and consequences using Architecture Decision Records (ADRs). It prevents knowledge loss, facilitates team communication, and maintains a historical record of critical technical choices.

Core Features & Use Cases

  • ADR Creation: Generates new ADRs following a structured template, including context, decision, consequences, and alternatives.
  • Historical Tracking: Helps maintain an evolving record of architectural history, crucial for onboarding and future decision-making.
  • Use Case: When deciding to migrate from a monolithic database to microservice-specific databases, use this skill to create an ADR documenting the context, the chosen solution, its pros/cons, and the rejected alternatives.

Quick Start

Create an Architecture Decision Record for choosing between a monorepo and polyrepo structure.

Frequently Asked Questions about architecture-decision-recorder

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

FAQPage Schema
What is an Architecture Decision Record and why should I use one?▼

An Architecture Decision Record (ADR) is a structured document that captures significant architectural decisions, their context, rationale, and consequences. ADRs prevent knowledge loss, enable team communication across projects, and create a historical record that guides future decisions and speeds onboarding.

How do I create and document an architectural decision?▼

Use the template-based ADR creation to structure your decision with context (background and problem), decision (chosen solution), consequences (tradeoffs and impact), and alternatives (rejected options). Store the ADR in source control as an immutable versioned record linked to related decisions.

Can I track architectural decisions across my team and link related ADRs?▼

Yes. ADRs support linking related records to build a connected history of decisions. Quarterly reviews with quantitative data help teams evaluate decision outcomes and maintain visibility into how architectural choices affect the project over time.

What's the best way to manage technical debt and design tradeoffs in documentation?▼

Document design tradeoffs systematically in ADRs by recording the pros and cons of each alternative considered. This approach makes technical debt visible, justifies past choices, and provides data for future refactoring or migration decisions.

When should I create an ADR versus just updating code comments?▼

Create an ADR for significant architectural decisions—technology choices, structural patterns, and major design tradeoffs affecting multiple teams. ADRs in source control provide immutable versioned records and cross-functional visibility; code comments capture implementation details.

Do ADRs work for monorepo versus polyrepo decisions and microservice migrations?▼

Yes. ADRs excel at documenting major structural decisions like monorepo versus polyrepo choices or monolithic-to-microservices migrations. Use them to record context, rationale for database-per-service patterns, rejected alternatives, and long-term consequences for architecture evolution.

Related Skills

Explore More Software Engineering Skills→
jtvarisjtvaris

architecture-decision

Generate Architecture Decision Records with context, constraints, and alternatives.

Community
Intermediate
Imad-OuteImad-Oute
2

mh-cto-sdlc-tech-retro

Evaluate architectural decisions against production outcomes to update ADRs and catalog technical debt.

Community
Advanced
bybren-llcbybren-llc
395

confluence-docs

Create standardized ADR, runbook, and architecture documentation templates.

Official
Intermediate
EngineerWithAIEngineerWithAI
4

architecture-decision-records

Create and manage Architecture Decision Records in multiple formats.

Official
Intermediate