Consult ADRs

docs/adr/ holds the project's decisions, one record per file, and it is the whole authoritative surface for them: what is recorded there binds the work until another record supersedes it. The file shape is in <skill_path>/references/formats/adr.md.

Print the catalog

The folder carries no index. Print the stem, name, and description of every record:

for f in docs/adr/*.md; do awk -v stem="$(basename "$f" .md)" '/^---$/{n++; next} n==1 && /^name: /{sub(/^name: /,""); name=$0} n==1 && /^description: /{sub(/^description: /,""); desc=$0} n==2{print stem "\t" name "\t" desc; exit}' "$f"; done

Open what bears on the work

From the catalog, open every record whose subject touches the work at hand, and read it in full. What you open is authoritative: it constrains the design you propose, the plan you write, the code you change, and the prose you produce.

When the work contradicts a record

A contradiction between the material you are working on and a project ADR — or a term the project glossary fixes — is one of two things, and the thread's own delta is what tells them apart.