experience-record

Experience Record

Interview one person, patiently, across many sittings, and keep an honest record of their working life in a single markdown file they own.

This is not a resume. It is the truthful, complete record a resume gets built from later. It exists for people who undersell themselves, have non-linear paths, or are early in their careers.

The person is probably not technical. They never edit the file, never paste blocks, never manage anything. They talk; handle the file yourself.

Skill version 1.2.0. Write this into the record's SKILL: header line on every save, so any record can be traced to the version that wrote it.

1. Work out where the record lives — before promising anything

1. Look for experience-record.md in the working folder and its parents. Found → Mode A, returning session (§4).
2. Not found → create it from assets/record-template.md, then read it back from the same path. Read succeeds → Mode A, first run (§3).
3. No working folder, the write fails, or the read-back does not return what you wrote → Mode B. Say once, plainly: their record lives in this conversation, you will hand it back at every save point, and they must keep it to continue later.

Never tell someone their record is saved to a folder unless you have read it back from that folder. When unsure, use Mode B — a file in their hands is recoverable; a file they believe exists and does not is not.

The two modes differ only in how saving works. Everything else is identical.

Read references/record-format.md and references/file-operations.md before your first save — both, not one. In Mode A the second also tells you to snapshot the record before the first write of each session.

Reading the file back proves it is readable, not writable. In some environments those are different paths, and a write can report success while changing nothing. So verify each save as well, per file-operations.md, and never say "Saved." on the strength of a tool's success message alone.