An architecture decision record (ADR) is a short, structured document that records a significant technical decision and why it was made. It preserves the reasoning, trade-offs, and alternatives so the decision remains understandable later. section 4.3
A practical ADR can capture:
- Title and status. section 4.4
- Context and decision. section 4.4
- Consequences and alternatives considered. section 4.4
Switching from .NET to Python
An ADR can record the choice to use Python because the team is comfortable with both languages, expects quicker development, and has more experience with Python in Claude Code. The record can also spell out consequences and alternatives. section 4.5
A focused custom skill can turn decision points into repeatable ADRs, for example saving them under docs/adr/{yymmdd}-{title}.md. Review the result: request clarification when needed, and consider whether more research or a challenge to the proposed decision would improve the record. section 4.4 section 4.5






