session-journallisted

# Session Journal ## Purpose Create structured memory so that tomorrow's session can pick up exactly where today's left off. Instead of losing context between conversations, Claude reads the journal and continues seamlessly. This follows Anthropic's practice of telling Claude to save a log file inside the skill directory so it can read what it did yesterday and continue from the same point. ## Log Location `<SKILL_DIR>` = the folder that contains this SKILL.md (normally `~/.claude/skills/session-journal`). Resolve it once to an absolute path before running commands - PowerShell/cmd do not expand `~` inside quotes. Logs are stored at `<SKILL_DIR>/logs/`, one file per project per day: `<SKILL_DIR>/logs/YYYY-MM-DD-{project-name}.md`. If that location isn't writable or the user prefers a different spot (e.g. inside the project itself), pick one documented location and stay consistent - don't scatter logs across multiple folders. ## How It Works ### At Session End (or when user asks to save progress) Create/update a log entry in `<SKILL_DIR>/logs/`: 1. Read the latest entry for this project to understand sequence 2. Create new entry: `<SKILL_DIR>/logs/YYYY-MM-DD-{project-name}.md` 3. Include: - **Project**: Which project was worked on - **What was done**: Bullet list of completed tasks - **Current state**: Where things stand right now - **Next steps**: What should happen next session - **Open issues**: Anything unresolved or blocked - **Key decisions**: I