From letter-for-my-future-self
Saves a structured "Letter to My Future Self" checkpoint to the .memory/ folder for context persistence between sessions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/letter-for-my-future-self:letter-checkpointThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill writes a session summary to `.memory/` for future context restoration.
This skill writes a session summary to .memory/ for future context restoration.
Invoke this skill when:
/letter-checkpoint or /checkpointCreate the .memory folder if it doesn't exist:
mkdir -p .memory
Determine the filename using timestamp format:
letter_YYYYMMDDHHMMSS.md (e.g., letter_20260321143022.md)Write the letter using the Write tool:
.memory/letter_YYYYMMDDHHMMSS.mdConfirm to user: Tell them the checkpoint was saved with the filename.
The content MUST follow this structure:
# Letter to Myself (Session Handoff)
**Date:** [Current date and time]
## 1. Executive Summary
* **Goal:** [One sentence on what we were building]
* **Current Status:** [Stopped at file X / debugging function Y]
## 2. The "Done" List (Context Anchor)
* Implemented [Feature A]
* Fixed [Bug B]
* Refactored [Component C]
## 3. The "Pain" Log (CRITICAL)
* **Tried:** [Library/Method that failed]
* **Failed:** [Error message or unexpected behavior]
* **Workaround:** [How we solved it]
* *Note:* Do not retry the failed method above.
## 4. Active Variable State
* Environment variables, ports, or temporary mock data
* Any config that was changed
## 5. Immediate Next Steps
1. [ ] Action item 1
2. [ ] Action item 2
3. [ ] Action item 3
npx claudepluginhub nyxcore-systems/letter-for-myself --plugin letter-for-my-future-selfSaves session state and writes a handoff note so the next Claude Code session can continue cleanly. Read/writes a remember.md file at the project root.
Persists task plans, findings, and progress as markdown files so work survives context loss and /clear. Use for multi-step projects or tasks requiring 5+ tool calls.
Generates and saves Markdown session logs capturing objectives, file changes, referenced materials, technical notes, future plans, open items, and metrics to resume project work across conversations.