technical-decision-record
<framework_overview>
What This Is
A structured approach to documenting technical decisions using ADRs (Architecture Decision Records). Ensures decisions are traceable, well-reasoned, and understood by the team.
When to Use
- Choosing between technologies or frameworks
- Making architectural changes
- Selecting third-party services
- Changing established patterns
- Any decision you'd want to reference later </framework_overview>
1. DECISIONS ARE IMMUTABLE HISTORY
Once made, an ADR is never modified—only superseded. This preserves the reasoning at the time, even if context changes later.
More from chaiwithjai/claude-code-mastery
standup-formatter
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
12code-review-preferences
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
11domain-expertise-template
Template for creating domain expertise skills. Copy and customize for your specific domain.
11example-skill
An example skill demonstrating the basic structure. Use when user asks about examples or templates.
10