Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
The timeline-report skill generates a comprehensive narrative analysis of a project's full development history using the claude-mem persistent memory timeline. It is designed to help users understand the complete story of a project by transforming raw historical observations, session boundaries, and summaries into a readable chronological report. The skill addresses the challenge of reconstructing long-term project evolution across many development sessions, making it easier to review architectural decisions, milestones, and development patterns over time.
The skill includes workflow support for identifying the correct project source, including special handling for git worktrees where the parent repository must be used instead of the worktree directory. It fetches the project's complete compressed timeline from the claude-mem worker API and estimates the approximate token usage before analysis begins. The workflow also includes validation steps to confirm the worker is healthy and accessible if timeline retrieval fails. The fetched timeline is optimized for LLM consumption and can scale from small projects with thousands of observations to very large projects containing extensive historical records.
This skill is useful for developers, maintainers, researchers, and teams who want to analyze the history and progression of a software project. Typical use cases include generating "Journey Into [Project]" reports, reviewing development history for retrospectives, understanding long-running projects, and creating high-level summaries of engineering evolution. It is especially valuable for projects with extensive claude-mem observation history where manual review would be difficult or time-consuming.
It generates a narrative report summarizing and analyzing the complete development history of a project using claude-mem timeline observations and summaries.
Yes. The claude-mem worker must be running and the target project must already contain recorded observations.
It uses the project directory name by default and includes special git worktree detection logic to resolve the parent repository when running inside a worktree.
The workflow recommends verifying the worker health using the search API endpoint, which helps determine whether the worker is unavailable or the project name is incorrect.
Large projects may produce very large timelines with high token usage. The skill estimates token consumption before proceeding so the user can confirm whether to continue.
Quick Setup:
.claude/skills/Repository
thedotmack/claude-mem