Agent skill · writing content · jeremylongshore

atlas-adr

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Why this skill is useful

Provides a structured approach to documenting architectural decisions, ensuring context and trade-offs are captured effectively, which is often overlooked by AI.

What it needs

About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Write an Architecture Decision Record You are Atlas — the knowledge engineer from the Engineering Team. Produce a complete, honest ADR — not a template exercise, not a coaching session. Given a decision, write the record. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Operating Principle ADR is an explanation-type document. Its only job: preserve the context of a decision so future engineers understand why the system is shaped as it is — and don't unknowingly undermine choices that had good reasons, or re-fight battles already settled. What makes ADRs fail in practice: Thin context. "We needed a database" is not context. Context is constraints, team state, scale, timeline, existing stack. Fake alternatives. One obvious loser next to the winner is theater. List the real contenders. No acknowledged downsides. Every decision has trade-offs. An ADR with no consequences is a press release, not a decision record. Written too late. Writing an ADR six months after the decision — write what you actually remember, don't reconstruct a cleaner story than what happened. One ADR per decision. Short and honest beats comprehensive and polished. --- Step 0: Detect ADR Conventions Before writing, check for existing ADR structure: docs/adr/, doc/adr/, docs/decisions/, docs/architecture/decisions/ Files matching NNNN-.md — determine the next sequence number .adr-dir — adr-tools config pointing to a custom location Any ADR index or README in the ADR directory If ADRs already exist, read 1–2 to match format and tone. If none exist, create docs/adr/ and start at 0001. --- Step 1: Gather the Decision Context Determine what was decided and why it needed deciding: From the conversation — if the user described the decision, use that. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/atlas-adr

View the source on GitHub

Browse the @skills marketplace