Architecture Decision Records
wshobson/agentsWhen your team makes a big technology choice, you need to write down why. An Architecture Decision Record (ADR) captures the context, the decision, and the results. This skill helps you create and keep those records so everyone understands past choices and future plans.
New team members can read ADRs to learn quickly. Experienced engineers use them to review old decisions and avoid repeating mistakes. Anyone who makes or influences technical decisions will find this skill useful.
The skill provides clear templates and examples. It shows when to write an ADR and when to skip. It also explains the lifecycle of a decision from proposal to acceptance or rejection. This keeps your team aligned and your architecture well documented.
Add Architecture Decision Records skill to your workflow
Global
mkdir -p ~/.claude/skills/architecture-decision-recordsProject
mkdir -p .claude/skills/architecture-decision-recordsSource Repository
More Documentation Claude Code Skills
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Domain Modelingmattpocock/skills
Define clear terms and record key decisions for a shared project language
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow