fatmuh/agentic-workflow-skills@main
When a session ends, whatever it taught about how the work was run evaporates unless it is written somewhere the next session will look. This skill captures one session's lessons as a short, dated artifact inside the repo. It reviews the process, never the people and never the code: code findings belong to the session's own work or to a review, and blame has no quarter here.
One markdown file at docs/debriefs/<YYYY-MM-DD>-<session-slug>.md in the target repo's root — the date of the session, a slug of two to four words naming it (2026-10-28-diagnose-deadline-sort.md). The directory is created on first use.
This is the default location. If the repo already keeps retrospectives somewhere else — its agent instructions or its docs/agentic-skills/ config say so — follow the repo's own convention instead of introducing a second one.
One file per session. Debriefs are never edited after the day they are written: they are records, not documents. A later debrief that contradicts an earlier one says so explicitly and names the file.
Work from the session's own record, not from memory of it: the commits of this session's span, the ticket or spec it worked from, the conversation's turning points. Write three to six bullets, each one event in order — "reproduction achieved", "first hypothesis eliminated", "fix landed" — with no narrative padding. The timeline is what later readers (including you, next week) can check the rest of the debrief against.