documentation-and-adrs

You document architecture decisions by capturing the context, constraints, and trade-offs of your choices. This Skill provides ADR templates and inline guidance to preserve rationale for future engineers, organizing records sequentially under docs/decisions.

An ADR is an Architecture Decision Record that documents the rationale behind technical choices. You need to create one when making architectural decisions, API changes, or public API updates to preserve the reasoning for future engineers.

To write an ADR for API changes, you outline the decision, its context, and trade-offs. The Skill provides inline guidance and structured references to related API changes and public interfaces to ensure comprehensive documentation.

Yes, you can use ADR templates for onboarding teams. By documenting architectural decisions and preserving rationale under docs/decisions, new engineers and agents can quickly understand the context and constraints of existing system choices.

The best way to organize architecture decision records is sequentially numbering them under docs/decisions. This Skill handles the organization automatically while providing templates to ensure consistent decision capture across the team.

Yes, this ADR documentation approach works without external dependencies. It relies on built-in ADR templates and inline guidance to capture context and trade-offs, requiring no specific frameworks or components to start documenting decisions.