Create Architecture Decision Record

To create an Architecture Decision Record safely, this Skill automates numbering and drafting while performing contradiction detection against accepted ADRs. It identifies scope overlaps across files and features to ensure new architectural decisions maintain consistency.

Documenting technical decisions to manage architectural debt requires capturing the context, decision, and status. This Skill guides you through decision capture and conflict resolution, writing the outcome to a strict ADR template in the Context/Decisions/ directory.

Contradiction detection for Architecture Decision Records works by comparing newly proposed decisions against existing accepted ones. The process identifies potential conflicts and scope overlaps across specific technical concerns within defined technology stacks to resolve issues proactively.

You need to create an ADR when a significant technical change is proposed in a software engineering project. Documenting the decision ensures architectural integrity, verifies compatibility with past choices, and provides historical context for future reference.

Yes, a strict ADR template is required to automate architecture documentation. Adhering to predefined rules and maintaining historical integrity ensures the automated generation produces consistent, valid records that align with your existing technology stack.

Yes, you can check if a new database access pattern conflicts with past architectural decisions. By drafting the proposed change with this Skill, it validates the new decision against existing ADRs to detect scope overlaps and technical conflicts.