skills.rest
nomos-guild
nomos-guildOFFICIAL
Explore all skills by this author →
GitHub

journey

Create session learning logs under .claude/journeys/ with title, date, summary, and key learnings.

4|2|Updated Oct 26, 2025
Search Tags:#documentation#learning#memory#claude-code#knowledge-management#journey
One-click install
npx skills add https://github.com/nomos-guild/cgov --skill journey-nomos-guild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/nomos-guild/cgov/tree/main/.claude/skills/journey
Command: npx skills add https://github.com/nomos-guild/cgov --skill journey-nomos-guild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a structured log of session learnings to preserve knowledge across Claude Code sessions, preventing loss of context when teams evolve or hand off work.

Core Features & Use Cases

  • Structured Journey Files: journey notes are saved under .claude/journeys/ with a timestamped filename and a clear title.
  • Comprehensive Content: each journey includes a title, date, summary, what was done, key learnings, and optional references to related files.
  • Use Case: after a major refactor or architectural decision, create a journey to capture decisions, outcomes, and lessons for future sessions.

Quick Start

Run the journey command to create a new log, then fill in the sections and save the file under .claude/journeys/.

Frequently Asked Questions about journey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve session memory across Claude Code projects?▼

To preserve session memory across Claude Code projects, you can create structured learning logs that capture architectural decisions and major pattern discoveries, storing them under .claude/journeys/ for future access.

What is the best way to maintain institutional memory during team handoffs in Claude Code?▼

Maintaining institutional memory during team handoffs requires logging session learnings in a structured format with title, date, summary, and key outcomes, preventing context loss when teams evolve or transition work.

How do I create a journey log after a major refactor in Claude Code?▼

To create a journey log after a major refactor, run the journey command to generate a timestamped file under .claude/journeys/, then fill in the title, summary, what was done, key learnings, and optional references.

What information should I include in Claude Code session learning logs?▼

Session learning logs should include a title, date, summary, what was done, key learnings, and optional references to related files to comprehensively capture decisions and outcomes for future sessions.

Does the journey capability require any external dependencies to work?▼

No, the journey capability requires no external dependencies, operating entirely within the Claude Code environment to store structured session logs in the .claude/journeys/ directory.

When should I not use session logs for knowledge management in Claude Code?▼

Session logs are not needed for minor edits or routine tasks; they should only be applied after significant work, architectural decisions, or major pattern discoveries to avoid cluttering the knowledge base.

Related Skills

Explore More Education & Research Skills→
antoinerswantoinersw

setup-reactive

Configure the Clean Claude Reactive System with state storage, routing hooks, and agent communication scripts.

Community
Intermediate
coderhzycoderhzy

team-sync

Synchronize team status, handoff, decision, and stand-up Markdown documents.

Community
Intermediate
codewithmukeshcodewithmukesh
640

learning-log

Record development insights with date, category, title, description, and affected files.

Official
Intermediate
Shockwave2kShockwave2k

code-memory-updater

Update CLAUDE.md with code-change insights from diffs.

Community
Intermediate