architecture-decision-records

You document architectural decisions by creating ADRs that capture Context, Decision, Alternatives, and Consequences. This skill structures those records and maintains an indexed log in docs/adr to ensure traceability across your project.

The ADR format for recording design choices consists of Context, Decision, Alternatives Considered, and Consequences. This standardized structure codifies why a path was chosen so new contributors understand the rationale.

You maintain ADR traceability by keeping a canonical index in docs/adr with automatic numbering. The skill updates this log whenever a new architectural decision is recorded, ensuring continuous project history.

Yes, you can capture decision moments automatically. The skill auto-detects architectural decision points during coding sessions and prompts you to create a new ADR to prevent losing critical choices in scattered chats.

You should use ADRs because PR discussions and chats scatter critical architectural choices, making them hard to find. ADRs turn decisions into structured, codified documents that live permanently with your codebase.

No specific dependencies are required to create architecture decision records. The skill operates independently to generate standardized ADR files and manage the index within your existing documentation structure.