architecture-decision-records

You can capture architectural decisions by triggering a command like "record ADR" during your session, which generates a structured Architecture Decision Record document with your current context.

The Michael Nygard ADR format structures decision records into four distinct sections: Context, Decision, Alternatives, and Consequences, ensuring the rationale behind code design choices is clearly documented.

Architecture decision records can be tracked through a lifecycle state progression from proposed to accepted, and eventually to deprecated or superseded, maintaining clear status traceability over time.

You should document architecture decisions as ADR files when comparing frameworks, libraries, API designs, or deployment strategies, preventing context loss and helping future developers understand past choices.

Architecture decision records are stored under a dedicated docs/adr directory alongside your source code, with auto-incremented numbering like ADR-NNNN to ensure organization and traceability.

No dependencies are required to generate ADR documents, as the skill operates independently to produce formatted files and manage their lifecycle states without external libraries.