decision-recordlisted

# Decision Record This repo (`eagerworks/skills`) keeps its architectural decisions as dated markdown files in `docs/decision-records/`. This skill is the authoritative process for writing a new one or editing an existing one correctly — filename, title shape, section structure, and cross-referencing all follow one convention across all 9 existing records, and this skill exists so that convention doesn't have to be rediscovered (or drift) every time. ## When a record is warranted Write one when the change is a **choice with a real alternative** that the code alone won't explain to a future reader — an output contract (where a skill writes, what its one write is), a naming or config convention, a workflow that deliberately deviates from an existing precedent, a lens or dimension added to a rubric, a resolution order for ambiguous input. Do **not** write one for: a routine edit, a typo/wording fix, anything already stated plainly in `CLAUDE.md` or `CONTRIBUTING.md`, or a decision with no real alternative anyone would have picked instead. ## Filename ``` docs/decision-records/YYYY-MM-DD--kebab-slug.md ``` - The date is the date of the decision (not necessarily today, if backfilling). - The slug names **the decision**, not the skill — e.g. `audit-report-saved-to-docs`, not `loop-engineering-audit-2`. - The filename is the record's identity and its sort order. Nothing else numbers it. ## Title and shape ```markdown # <One declarative sentence stating the decision> - **