documentation-and-adrs

Document decisions, not just code. The most valuable documentation captures the why — the context, constraints, and trade-offs that led to a decision. Code shows what was built; documentation explains why it was built this way and what alternatives were considered. This context is essential for future humans and agents working in the codebase.

When NOT to use: Don't document obvious code. Don't add comments that restate what the code already says. Don't write docs for throwaway prototypes.

ADRs capture the reasoning behind significant technical decisions. They're the highest-value documentation you can write.

アーキテクチャの決定、パブリック API の変更、機能の出荷を行う場合、または将来のエンジニアやエージェントがコードベースを理解する必要があるコンテキストを記録する必要がある場合に使用します。 ソース: addyosmani/agent-skills。