tack-adr

Installation
SKILL.md

tack-adr: decisions as committed text

ADRs are where "we decided this, and here is why" lives: plain Markdown in docs/adr/, versioned with the code, linked from AGENTS.md. In the tack workflow they are the resolution tool for drift B ("the standard was wrong — change it") and a required artifact for any behavior change found during migration. If it isn't in an ADR, the next agent will re-litigate it.

When to write an ADR

  • A change in observable behavior (public API, semantics, data formats)
  • A new target standard or convention (consistency catalog row)
  • A tooling, dependency, or architecture choice
  • A drift-triage outcome of "change the standard"
  • Anything you do not want re-debated in six months

Not for: routine PRs, per-file explanations (those are code comments), or one-off tasks. Details: references/adr-practice.md.

Installs
–
Repository
tacoda/tack
First Seen
Today