Agent skill · product strategy · aiskillstore
technical-decision-record
Use when making technical decisions, choosing technologies, or documenting architectural choices. Creates ADRs (Architecture Decision Records).
Why this skill is useful
Codifies a structured approach to documenting architectural decisions that the AI could infer but doesn't have a standard for.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
<frameworkoverview> 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 </frameworkoverview> <principles> Core Philosophy 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. 2. CONTEXT OVER CONCLUSION The "why" is more valuable than the "what." Future readers need to understand the constraints, options, and trade-offs that led to the decision. 3. BIAS TOWARD REVERSIBILITY Prefer decisions that can be changed later. Document the reversal cost for irreversible choices. 4. EXPLICIT OVER IMPLICIT If it wasn't written down, it wasn't decided. Verbal agreements don't count as architectural decisions. 5. TEAM OVER INDIVIDUAL Decisions should be reviewed by affected parties. Surprise decisions create resistance. </principles> <process> The Process Step 1: Define the Problem What are we deciding? Be specific. "Which database for user data" not "database stuff" Include the trigger: what prompted this decision? Step 2: List Constraints What limits our options? Technical: performance, scalability, existing stack Business: budget, timeline, team skills Compliance: security, regulatory, data residency Step 3: Enumerate Options List 2-4 real options. For each: Brief description Pros (what it does well) Cons (what it does poorly) Estimated cost/effort Step 4: Make the Decision Choose one option. State it clearly. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/technical-decision-record