adr-capture
Catch an architectural decision as it is made and draft an ADR in your team's format, with explicit TODOs for missing mandatory fields. Never auto-commits.
Install
$ curl -fsSL https://raw.githubusercontent.com/Osipchuk/agent-skills/main/install.sh | sh -s -- adr-captureOne line, works with any agent — installs just this skill into ~/.claude/skills/. Needs only curl; it fetches uv and the askill CLI if they're missing.
$ /plugin marketplace add Osipchuk/agent-skills
$ /plugin install skills@askillTwo slash commands inside Claude Code — installs the whole library as one plugin and lets Claude pick the right skill by context. No permission prompts, no remote-code-execution dance.
Installs skills/adr-capture/SKILL.md into
~/.claude/skills/adr-capture/; Claude reads it on the next
session start. The plugin tab pulls the whole library instead.
When it fires
Fires on an explicit request ("draft an ADR", "record this decision") and proactively when the conversation shows a commitment plus a rationale ("we'll go with X over Y because Z"). It assigns the next id, fills what was said, and flags mandatory regulated sections as TODO. It stays quiet during exploratory discussion and never writes without confirmation.
name: adr-capture
description: Catch an architectural or technical decision as it is being made and draft an Architecture Decision Record (ADR) in the team's format, leaving explicit TODOs for fields the conversation did not cover. Never writes or commits without explicit confirmation. Use this when the user asks to "draft an ADR", "record this decision", "capture this as an ADR", AND proactively offer it when the conversation shows a commitment pattern — "we'll go with X over Y because Z", "let's standardize on...", "decided to...", "we're choosing..." — paired with a rationale. It assigns the next ADR id, fills what the discussion supports, and flags team-mandatory sections (e.g. regulatory impact, data classification, rollback plan) as TODO when missing. Do NOT use for: exploratory discussion with no commitment ("we might try", "could consider", "what if we"), non-architectural decisions (scheduling, naming, trivial style), or generating product/requirements specs. When unsure whether a real decision was actually made, ask one question rather than draft.
What it does
- — Catches the decision while it's warm — the friction of writing ADRs by hand is exactly why they don't get written.
- — Biases to false negatives: asks once rather than spamming the log with drafts of things merely floated.
- — Knows your mandatory sections (regulatory impact, data classification, rollback) and TODOs them rather than inventing content.
- — Review-then-write: drafts in chat, writes only on confirmation, never past Status: Proposed.