Document architectural decisions using the Design It! ADR methodology.
npx skills add https://github.com/timblaktu/nixcfg --skill adr-writer-timblaktu
Please help me install this Agent Skill. Skill: adr-writer Source: https://github.com/timblaktu/nixcfg/tree/main/home/modules/claude-code/skills/adr-writer Command: npx skills add https://github.com/timblaktu/nixcfg --skill adr-writer-timblaktu
ADRs are essential but often inconsistently documented, leading to ambiguity and miscommunication about architectural decisions. This Skill provides a clear template and guidelines to ensure decisions are recorded clearly and consistently.
Create a new ADR file (e.g., docs/adr/0001-record-architecture-decisions.md) and populate it with the ADR template provided by this Skill.
High-intent search queries and answers about installing and using this skill.
An Architecture Decision Record (ADR) documents architectural decisions by structuring context, tradeoffs, and rationale into Status, Context, Decision, and Consequences sections. This ensures clear communication and prevents ambiguity across project teams.
The best way to write an ADR for version control is to place repository-friendly markdown files in a dedicated directory like docs/adr/. This enables traceability and team collaboration on architectural decisions directly within the codebase.
An architecture design doc for tradeoffs should include Status, Context, Decision, and Consequences sections. This structure promotes thorough reasoning about architectural choices and documents future evolution impacts clearly.
To start recording software design decisions using the Design It methodology, create a new markdown file in your repository and populate it with the provided ADR template to guide your documentation of context and consequences.
You need to create an ADR when making significant software architecture decisions that require documented context, tradeoffs, and rationale. Recording these decisions prevents miscommunication and provides traceability for future team members.
caobingshengWrite and edit Markdown documentation following Gemini CLI project standards.
nselugaCollaboratively define and standardize project domain terminology and record architectural decisions.
stark-ai-deInterview users to capture requirements and draft Codex-executable implementation specs.
LetPeopleWorkDocument architecture decisions and patterns using ADR templates.
