dev-memory-briefing

A session briefing synthesizes recent events and sessions from your repository's ai_memory files into a structured snapshot. Provide your repo path and optional filters (branch, epic_id, issue_id) to extract timeline context, open questions, and recommended focus areas for starting or resuming work.

The briefing processes events.jsonl and sessions.jsonl from your ai_memory directory, parsing stored development events and sessions. It filters by time window (days_back), event count (max_events), and scope (epic or issue) to produce a prioritized view in markdown or JSON format.

Generate a briefing at session start to rebuild context, during onboarding to understand project state, before planning or reviewing issues to ground decisions, and at context refresh when resuming work after time away.

Yes. The briefing accepts optional branch, epic_id, and issue_id parameters to narrow scope. You can also control time range (days_back) and result density (max_events) to create focused briefings for targeted work.

The briefing generates output in both markdown and JSON formats, letting you choose the structure that fits your consumption workflow—markdown for readable reports or JSON for programmatic integration.

The briefing validates memory file existence and handles empty or missing event logs gracefully, returning a valid structured output with appropriate indicators of missing data rather than failing.