build-session-context

To summarize project logs for quick context, you can aggregate key metrics from files like CLAUDE.md, TASK_BOARD.md, and GIT_LOG.md into a compact narrative. This extracts essential fields like recent commits, migration progress, and blockers to provide a token-efficient status snapshot.

The best way to generate a project status snapshot for onboarding is to extract essential fields such as phase, last updated date, and recent commits from multiple project logs. This produces a concise 1-2 paragraph narrative suitable for daily standups and quick re-engagement.

Yes, you can aggregate migration progress and blockers from multiple markdown logs. The process reads files like MIGRATION_LOG.md and DEBUG_LOG.md, extracts the relevant status fields, and outputs a single compact overview of project health.

Generating a session context summary relies on reading specific markdown log formats like CLAUDE.md, TASK_BOARD.md, MIGRATION_LOG.md, DEBUG_LOG.md, GIT_LOG.md, and SKILLS_LOG.md to extract phase, recent commits, and blockers.

You use a log aggregation summary instead of reading files directly to save time and tokens during session startup. It delivers a compact narrative of project health, preventing the need to manually scan every log file to understand the current state.

The limitation of using automated project log summaries for a post-break resume is that the output is a concise narrative focused only on essential fields like phase, recent commits, and blockers. It may omit granular details required for deep debugging not present in the aggregated logs.