What problem does it solve?
This Skill solves the problem of losing critical context around technical and architectural decisions, which leads to repeated team debates, slow onboarding for new engineers and AI agents, and inconsistent implementation of project standards across the codebase.
Core Features & Use Cases
- Architectural Decision Records (ADRs): Capture the full context, trade-offs, and rationale behind major technical choices (e.g., selecting a database, authentication strategy) to avoid re-debating old decisions.
- Inline Code Documentation: Guide teams to write meaningful "why" comments instead of redundant "what" comments, and document known gotchas to prevent common errors for future maintainers and agents.
- Project Documentation Standards: Provide templates and best practices for READMEs, API docs, and changelogs to ensure consistent, useful documentation across the project.
For example, when your team chooses to switch from REST to GraphQL for your public API, use this Skill to create a formal ADR that records all considered trade-offs, the final decision, and its long-term consequences, so future team members and AI agents don't waste time re-evaluating the same choice.
Quick Start
Use the documentation-and-adrs skill to create a formal ADR for your team's recent decision to adopt PostgreSQL as the primary database, including all context, trade-offs, and consequences.
