Learnings

Teach the decisions and diagnostic checks the reader can reuse from work a coding agent performed, so they gain the lesson without having struggled through the problem. Explain what they would notice, consider, and check, rather than recounting agent activity.

Period and scope

• Honor the requested period and scope. Default to today, local midnight through now, in the user's timezone. Default to the current project, or the working directory outside a project.
• Resolve relative dates against the user's current date. Weeks start Monday unless specified otherwise; explicit date ranges include both dates. State the resolved period and timezone. If the timezone is unavailable, disclose the local timezone used. Ask only when ambiguity materially changes the review.
• A topic alone filters the default scope; it does not broaden the review across projects.
• Include associated worktrees and resumed sessions using canonical paths and repository metadata, not folder names alone.
• Default to the running agent's history. Read other agents' accessible local logs only when explicitly requested, honoring whether they replace or supplement the default source. Keep the period and project filters; an all-projects request alone does not include other agents.
• For an explicit all-projects request, discover projects from the selected agents' accessible history and identify the project for each lesson.

Find and assess evidence

1. Locate each selected agent's history through available tools, runtime context, configuration, or user-provided log paths. Inspect each source's format; agents can use different storage layouts and schemas. Skill installation paths are not necessarily log paths. Report unavailable sources and continue with accessible evidence. Use the current conversation only if it matches the selected agents, period, and project scope. If no usable evidence is available, report that limitation. Do not scan the filesystem indiscriminately or change permissions to gain access.
2. Use indexes and summaries to find candidate sessions, then inspect their transcripts and tool results. Follow pagination and check archived sessions where supported before claiming complete discovery. Distinguish sessions found from those inspected in depth.
3. Filter by actual message and tool-event timestamps in the user's timezone. Session start dates and file modification times are only discovery hints; older sessions can contain work in the requested period.
4. Trace relevant failures, hypotheses, checks, decisions, corrections, and verification. Include incidents with investigation, decision, correction, or verification in the period. Label any earlier context or later follow-up used to explain them.