Architecture Decision Record Manager

•
31
•

Records, validates, and manages Architecture Decision Records (ADRs) to preserve settled technical conventions across developer workflows.

The Architecture Decision Record (ADR) skill automates the lifecycle of architectural governance within code repositories using fabrika CLI tooling. It safely allocates non-colliding numeric IDs across distributed git branches, scaffolds standardized decision templates, scans existing records to prevent contradictions, and updates cross-record statuses like superseding or amending older rulings. This skill is critical whenever engineering teams settle architectural debates, establish invariant conventions, or introduce new technical standards that future AI agents and human contributors must strictly observe.

Características Principales

01Seamless terminology routing and vocabulary synchronization for technical glossaries
02Atomic ID minting across local branches, worktrees, and remote pull requests to prevent collisions
03Automated contradiction sweeping against live, accepted architectural decisions
04Precise reference verification and automated status transitions for superseding or amending records
0531 GitHub stars
06Structured scaffolding with standardized decision syntax and binding constraint blocks

Casos de Uso

01Preventing concurrent ID allocation conflicts when multiple developers or agents propose ADRs simultaneously
02Recording irreversible technical trade-offs, invariants, and settled standards during architectural planning
03Deprecating or amending existing system decisions when updating infrastructure or coding standards