architecture-decision-records

To document architectural decisions during coding sessions, you can initiate the recording process by stating your intent to capture the decision. The skill automates capturing the context, alternatives considered, and consequences, requiring your confirmation before creating the file.

Architectural decision records are needed for codebase maintenance to preserve the rationale, alternatives, and outcomes of past choices. They maintain project integrity by ensuring development teams share a clear understanding of architectural history and reasoning.

The best way to structure architectural decisions for team clarity is to maintain a structured directory of decision records. This approach systematically organizes the decision context, alternatives considered, and consequences for future reference.

Yes, you can retrieve historical architectural decisions to understand why a specific codebase choice was made. The skill provides an interface allowing team members to quickly access past records, preserving the original context and rationale.

To start recording an architectural decision, simply state "Let's record this decision" or "ADR this" during your coding session. This triggers the interface for capturing the decision context, alternatives, and consequences.

No, you do not need to manually organize files when documenting architectural decisions. The skill maintains a structured directory of decision records automatically, though it requires your confirmation before actually creating any files.