What problem does it solve?
Architectural decisions often go undocumented or get lost in PR discussions, leaving future team members unable to understand why a design choice was made. This Skill produces a properly formatted, sequentially numbered ADR file capturing the decision, its context, and its consequences.
Core Features & Use Cases
- Sequential ADR numbering: Scans the existing
adr/ directory, finds the highest number, and assigns the next zero-padded identifier (e.g., 0002).
- Structured template: Uses the Nygard ADR format (Status, Context, Decision, Consequences) with optional Considered Options and Rationale sections, loaded from
assets/adr-template.md.
- Guided information gathering: Extracts decision details from design docs or PR discussions when available, or asks targeted clarifying questions.
- Use Case: After deciding to host eval assets on HuggingFace Hub, ask the assistant to record the decision; it creates
adr/0003-use-huggingface-for-assets.md with full context, alternatives considered, and consequences.
Quick Start
Ask the assistant to write an ADR documenting the decision to use HuggingFace Hub for asset hosting, including the alternatives considered.