git:20260925.cb72780 to git:20260926.7dce66c

16 added, 13 removed. Audit A to A.

---

name: adr-verbatim

- description: 'Write a new ADR whose body is the user''s exact words, nothing added. Use when the user says "adr-verbatim", "document that as an ADR", "new ADR", "record this decision", or gives wording for an ADR. Differentiator: agent adds only title, number and status line; it never drafts, rewrites, or expands the body.'

+ description: 'Record concise ADRs that preserve the user''s decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.'

---

# ADR Verbatim

- The body of the ADR is the user's words, pasted exactly as given. Not one word added, removed, or fixed.

+ Preserve the user's meaning, not the conversation transcript. Record only the decision and context needed to understand it.

## Steps

- 1. If the user gave no wording, ask them for it in plain text. Never draft the body yourself.

- 2. Read `docs/adr/` and take the next number. Follow the existing naming style: `docs/adr/0042-short-slug.md`.

- 3. Write the file:

+ 1. Extract the decision the user stated or approved in the conversation. Ask only if the decision is unclear; do not require the user to dictate polished wording.

+ 2. Use the project's established ADR location, including a previously specified repository. Do not assume the current checkout owns the ADRs. Read that directory and take the next number.

+ 3. Write a short, clear ADR. Remove filler, emotional reactions, repetition, rhetorical questions, and instructions to the agent. Fix grammar and clarify references without changing the meaning, scope, conditions, or priorities.

+ 4. Check every statement against the user's decision. Remove invented requirements and unapproved agent suggestions.

+ 5. Show the saved path and full ADR in a code block.

+ ## Format

+ Follow existing numbering and filenames, such as `docs/adr/0042-short-slug.md`.

```markdown

# 0042 — short title

Status: accepted (user, YYYY-MM-DD)

- <user's words, verbatim>

+ <The decision in plain English.>

```

- 4. Show the user the full file in a code block.

## Rules

- - Body = the user's words only. Keep their typos and grammar.

- - No Context / Decision / Consequences sections unless the user wrote them.

- - No bullet lists, no summaries, no "why this matters", no alternatives.

- - Title and status line are the only text you write. Keep them under ten words.

- - Never edit an old ADR to change history. A new decision is a new ADR.

+ - Prefer a short paragraph or list. Add sections only when they improve clarity.

+ - Do not add speculative rationale, alternatives, consequences, or implementation details.

+ - Use exact wording only when the user explicitly asks for an exact quote or verbatim passage.

+ - A changed decision needs a new ADR. Correct an existing ADR when the user explicitly requests it, without changing unrelated history.