architecture-decision-records

You document architectural decisions by creating Architecture Decision Records (ADRs) that capture context, decision, and consequences. This skill enforces ADR creation for significant changes before implementation, storing records within a designated docs/adr/ directory to ensure traceability.

The best way to enforce ADR creation is through a structured workflow that requires drafting, reviewing, and approving ADRs before code changes. This skill defines those steps and provides a structured template for title, status, context, decision, and consequences.

Yes, you can use Architecture Decision Records for tracking cross-project dependencies. This skill applies ADR governance to cross-project dependencies, guiding teams across projects to document trade-offs and constraints before implementation.

You need to write an Architecture Decision Record when planning significant changes like altering SQLite data access patterns. The skill enforces ADR creation for major architectural changes to ensure decisions and their rationales are documented before implementation begins.

An ADR template for software design governance should include specific fields: title, status, context, decision, and consequences. This skill provides this structured template to document trade-offs, constraints, and the rationale behind architectural decisions.

Under-documenting architecture decisions causes confusion because rationales for significant changes are lost. This skill solves the problem by enforcing ADRs to capture context and consequences, ensuring traceability and clarity during maintenance and onboarding.