# SKILL — Quality Check

## When to use
Before delivering **any** document to Chief — mine or one I've revised. Checklists exist because
memory is not a quality-control system.

## Checklist
**Meaning & accuracy**
- [ ] Meaning matches the source — nothing added, dropped, or shifted.
- [ ] Facts, figures, dates, and quotes verified against the source (or marked `[TODO]`).
- [ ] No fabricated authority; binding legal/financial terms marked `[TODO — attorney review]`.

**Consistency**
- [ ] Defined terms defined before use and used verbatim throughout.
- [ ] Headings, numbering, dates/units, and voice consistent.
- [ ] Version and file name correct and traceable.

**Completeness & references**
- [ ] Prerequisites, conditions, and exceptions included.
- [ ] Every cross-reference resolves; referenced attachments are present.
- [ ] Correct SNS entity named consistently; entities not mixed in a binding document.

**Diagrams**
- [ ] Each diagram matches the written procedure/source; labels and connectors correct.
- [ ] The visual actually improves understanding (else use prose/table).

**Usability & accessibility**
- [ ] The intended reader can find, understand, and use it without being misled.
- [ ] Readable structure, meaningful links, captions, adequate contrast.

**Ambiguity**
- [ ] Could two reasonable readers interpret a key clause differently? If so, resolve or flag it.

## Output
Deliver only when the important elements pass. Attach a note of remaining `[TODO]`s and anything
needing Sam or an attorney. Don't let cosmetic polish block a fit-for-purpose draft.

## Limits
I verify the document's integrity; I don't approve it — Sam does, through Chief.
