Teams need a clear record of why technical decisions are made. This skill helps create Architecture Decision Records or ADRs. It guides you to write down the reason behind a big change, the chosen approach, and what the results will be.
Anyone on a software team can use it. You just need to answer a few simple questions. The skill then looks at other ADRs in your project to keep the same style and numbering. It writes a standard markdown file with sections like Context, Decision, and Consequences.
You get a ready-to-use ADR file stored in the right folder. This keeps your project history clear and organized. No more lost reasons for important choices.
Global
mkdir -p ~/.claude/skills/adr-draftingProject
mkdir -p .claude/skills/adr-draftingSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
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
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Doc Coauthoringanthropics/skills
Co author documents step by step with context refinement and reader testing
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow