What problem does it solve?
This Skill addresses the need to document small, implementation-level technical decisions that don't warrant a full Architecture Decision Record (ADR), preventing the loss of valuable context about "why" certain choices were made.
Core Features & Use Cases
- Lightweight Decision Records: Captures implementation choices like library selection, algorithm approach, or data structure.
- Searchable Log: Creates a cumulative, searchable log of developer decisions.
- Use Case: When deciding to use
dataclasses instead of TypedDict for DTOs, you can quickly create a decision record detailing the context, the chosen approach, and alternatives considered.
Quick Start
Create a new developer decision record with the title "Use dataclasses instead of TypedDict for DTOs", the context "We need a clear and concise way to represent data transfer objects that supports type hinting and immutability.", and the chosen decision "Chosen dataclasses for their built-in support for immutability and cleaner syntax compared to TypedDict.".