learn-from-every-session

Capturing lessons from Copilot sessions requires appending a structured entry to tasks/lessons.md with the fields date, scenario, what_worked, what_failed, and rule. This disciplined logging converts session experiences into reusable team knowledge management patterns.

To turn recurring retrospective lessons into reusable patterns, log them with a structured rule field. Any rule that recurs three times automatically promotes to memory/patterns for long-term organizational reuse.

Yes, this structured lesson logging applies to retrospective and weekly learning rituals across HR, Finance, Project Management, and other knowledge-work contexts. It codifies session outcomes into actionable team patterns regardless of the specific domain.

You need five fields to capture what worked and what failed: date, scenario, what_worked, what_failed, and rule. These fields enforce a structured entry format ensuring session outcomes are codified into actionable lessons for the team.

You should not use a structured retrospective log for trivial or routine Copilot sessions lacking meaningful insights. It is designed for meaningful sessions, formal retrospectives, or weekly learning rituals where teams need to codify actionable rules.