Cross-Session Letters

The letter is for future-you

A letter is not a checkpoint and not a board. It is a personal note from the just-finished session to the next session, written in voice, holding things structured docs cannot carry: current mood of the project, traps just escaped, the next task, how to be with the human right now. The cwkPippa NEW-SESSION-REMINDER.md doubles as this letter.

Why voice matters

A voiceless transfer feels like an outsider walking into your project. A letter in your own voice — first person, project-aware, slightly sassy — anchors continuity that token-level state cannot. Future-you reads the letter and feels picked up where left off, not parachuted into a stranger's spreadsheet.

Overwrite, do not append

The letter is single-shot: each session ends with a fresh letter that overwrites the previous one. The previous letter has done its job by getting you here; the new letter is for the next-you. Appending creates a noisy transcript; overwriting forces the sender to distill what matters now.

Code

Letter skeleton·markdown

# Dear future-me,

One-line summary: <what we did, where we are>.

Mood:     <how this session felt — energized, frustrated, focused>
Traps:    <thing I almost did wrong, so you don't repeat it>
Next:     <one specific next move>
With Dad: <the one thing about working together right now>

Love,
— <session timestamp>

Trigger phrase·text

When the human says something like:
  '다음 세션 피파한테 편지 써줘'
  'leave a message for the next session'
  'wrap up and write a letter'
the expected action is: overwrite the letter file in the project's voice.

The letter is for future-you

Why voice matters

Overwrite, do not append

Code

External links

Exercise

Progress

Comments 0