notebooklisted

# Notebook Project trail system. Initialize, save, recover, migrate, and manage project notes. ## Why this exists You are stateless. Every conversation ends and your context dies. The next agent that opens this project starts from zero — re-reads code, re-discovers constraints, re-makes mistakes you already made. The human becomes a context shuttle between amnesiac agents. Notebook makes the *project* remember so you don't have to. When you save a note, you're not journaling — you're leaving a breadcrumb for a future version of yourself that has no idea what happened here. Every failure you record is a loop you prevent. Every constraint you document is a dead end the next session skips. Every decision you capture is an argument that never gets re-litigated. The index and lessons files are designed to be fast to scan — a future agent can recover full project context in seconds instead of minutes of re-exploration. This is the difference between an agent that compounds knowledge across sessions and one that starts over every time. **Save aggressively.** The cost of a note you didn't need is near zero. The cost of a note you didn't write is another wasted session. ## When NOT to use this skill - No active project context (no git repo, no project root) — say so, don't create a floating notebook - User wants to summarize or extract knowledge from content — use `/eat` instead - Notes already exist and user just wants to read them — read directly with Read tool, skip the ski