This one keeps you from re-litigating the same architectural decisions every six months. It pushes you to write ADRs when choosing databases, frameworks, or API patterns, with a solid template that captures context, alternatives considered, and consequences. The inline documentation guidance is spot on: comment the why, not the what, and document gotchas that will bite future engineers or agents. Includes practical templates for API docs, READMEs, and changelogs. The "common rationalizations" section cuts through the usual excuses about self-documenting code. Most valuable for teams that keep rebuilding context from scratch because nobody wrote down why they picked PostgreSQL over MongoDB.
npx skills add https://github.com/addyosmani/agent-skills --skill documentation-and-adrs