adr-skill

Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.

Install
npx skills add 'https://github.com/vercel/ai/tree/main/skills/adr-skill'
Download bundle ↓
main · 8b92ba9Scanned 2026-09-15

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗
View on GitHub
← Back to SKILL.md

status: '{proposed | accepted | rejected | deprecated | superseded by title}' date: { YYYY-MM-DD } decision-makers: '{list everyone who owns the decision}'

{short title, representative of solved problem and found solution}

Context and Problem Statement

{Why does this decision need to happen now? What constraints exist? Include enough background that someone (or an agent) reading this for the first time can understand without follow-up questions.}

Decision

{What are we choosing to do? Be specific — include scope and non-goals.}

Consequences

  • Good, because {positive consequence}
  • Bad, because {negative consequence}

Implementation Plan

  • Affected paths: {files and directories that change}
  • Dependencies: {packages to add/remove/update}
  • Patterns to follow: {existing code patterns to match}
  • Patterns to avoid: {what NOT to do}

Verification

  • {how to confirm the decision was implemented correctly}
  • {another verification criterion}

Alternatives Considered

  • {Alternative 1}: {Why it was rejected, in one or two sentences.}
  • {Alternative 2}: {Why it was rejected.}

More Information

{Related ADRs, PRs, issues, docs, or conditions that would trigger revisiting this decision.}

Referenced from SKILL.md