What template does this skill use?

It uses a comprehensive template including sections for Context, Decision, Consequences (positives/negatives), Linkbacks to specs, and a Behavior Delta.

How does the skill handle file numbering?

The skill scans the docs/ADRs directory for existing files, sorts them numerically, and automatically increments the number for your new record (e.g., 0001, 0002).

When should I use the ADR skill?

Use it whenever you are making significant changes to system behavior, API contracts, tenancy/RLS, or any integration that impacts the project's long-term architecture.

An Architecture Decision Record (ADR) is a document that captures a significant architectural decision made along with its context and consequences, serving as a historical log for the project.

Where does this skill store the ADR files?

The skill automatically generates and stores markdown files within the docs/ADRs/ directory of your project.

Architecture Decision Records

Name: Architecture Decision Records
Author: mcart13

bymcart13

Aprendizaje y Documentación

Standardizes the creation and management of Architecture Decision Records (ADRs) within the TCC framework.

Acerca de

The ADR skill enables developers to document significant architectural choices, system behaviors, and infrastructure changes systematically. It automates the process of identifying the next sequential record number and provides a structured markdown template that captures vital context, decisions, consequences, and behavior deltas. This ensures that every major shift in system contracts, security posture, or data retention is recorded for long-term maintainability and team alignment.

Características Principales

Detailed tracking of positive outcomes and negative tradeoffs
Standardized templates for architectural and security decisions
Built-in behavior delta reporting for system changes
Automatic sequential numbering for new ADR files
Categorized documentation for infra, API, and compliance
0 GitHub stars

Casos de Uso

Documenting changes to system behavior, contracts, or operations
Recording data retention policies and RLS implementation details
Tracking compliance evidence and audit posture for security reviews

Acerca de

Características Principales

Detailed tracking of positive outcomes and negative tradeoffs
Standardized templates for architectural and security decisions
Built-in behavior delta reporting for system changes
Automatic sequential numbering for new ADR files
Categorized documentation for infra, API, and compliance
0 GitHub stars

Casos de Uso

Documenting changes to system behavior, contracts, or operations
Recording data retention policies and RLS implementation details
Tracking compliance evidence and audit posture for security reviews