adr-engineering

Record architecture decisions with ADRs.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/0xzahed-adr-engineering

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Record architecture decisions with ADRs. Use when making or reviewing significant technical choices.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/adr-engineering

What's inside

Skill name: adr-engineering
Description: Record architecture decisions with ADRs. Use when making or reviewing significant technical choices.
License: MIT
Metadata: tags: adr, engineering
Instructions: 33 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# ADR Engineering

## Use this skill when
- Capturing the why behind technical decisions
- Reviewing past decisions and alternatives
- Onboarding context

## Do not use this skill when
- Trivial implementation details
- A stale doc nobody updates (keep lean)

## Instructions
1. Title the ADR with the decision, not the debate.
2. Include context, decision, alternatives considered, and trade-offs.
3. Date and number ADRs; link superseded ones.
4. Keep ADRs short enough to stay maintained.
5. Add status: proposed, accepted, superseded.
6. Review ADRs at design checkpoints, not after.

## Checklist
- Why recorded
- Alternatives documented
- Status maintained

## Output Format
- ADR | status | context | decision | trade-offs

## Common Mistakes
- ADRs written to justify after the fact
- Epics documents nobody rereads
- No supersession tracking

From 0xzahed/antigravity-skills, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/0xzahed/antigravity-skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from 0xzahed

Cite this page

adr-engineering skill. Agent Mart. https://agentmart.dev/skills/0xzahed-adr-engineering (last updated 2026-10-24)