What problem does it solve? When working with coding agents across sessions, decisions, changes, and verification steps are easily lost. This Skill preserves what happened in a session as a structured Markdown log so you or a teammate can reconstruct the work weeks later. ## Core Features & Use Cases - Two-layer destination strategy: Writes logs into an Obsidian vault with daily-note links, tags, and graph integration when configured, or falls back to a plain logs/ directory when Obsidian is unavailable. - Structured log template: Captures goal, decisions, work performed, verification, related notes, and next actions with consistent frontmatter and timestamped filenames like LOG_2026-01-15T0930 API Migration.md. - Related context search: Searches prior logs with ripgrep and links relevant earlier entries so the history of decisions stays connected. - Use Case: After finishing a debugging session, ask the agent to log the work; it records the root cause, files changed, and test results, then links the entry from today's daily note in your Obsidian vault. ## Quick Start Ask the agent to create a session log with a short theme, for example: create a session log for the API migration work we just finished.