session-journal

Session journaling preserves context by logging architectural decisions and rationale to a standardized markdown file with timestamps at the start of and during work sessions.

Capturing project lessons involves loading existing lesson files from a workspace memory directory at session start, then detecting recurring patterns at session end to trigger automated lessons-capture for future application.

You can track session progress and identify open threads by generating an end-of-session summary that notes accomplishments, lists unresolved items, and detects recurring patterns within your project workspace.

Yes, you need a workspace memory directory to store and retrieve project lessons. The skill loads lessons from a designated workspace path and logs decisions to a structured brain directory during active work.

During design reviews, decision logging works by recording significant choices to a dated markdown file with timestamps and rationale, creating a chronological record of architectural and design decisions within the conversation context.

Yes, markdown files are used for session logging and context management. Decisions are recorded in a standardized markdown format with timestamps, rationale, and open threads for cross-session continuity.