compound-retros

Capture one durable lesson from finished work as a short structured note in the repo's solutions store (default docs/solutions/, honoring existing conventions) — the problem hit, the cause or key decision, the fix or pattern applied, and what to avoid next time, including lessons the user taught by correcting, rejecting, or rewriting agent output. Use this skill after meaningful work worth remembering, when the user says "lưu lại bài học", "ghi chú lại", "rút kinh nghiệm", "remember this", "note to self", when they corrected or rewrote agent code with an implicit convention, after a hard debugging session or real trade-off decision, or when the same problem appears for the second time. Skip it for trivial tasks (typo, one-off environment hiccup), anything already explained by the final code, tests, docs, or AGENTS.md, and anything the user asked not to record; never write secrets, credentials, or sensitive values into notes.

Make past lessons compound before starting non-trivial work — locate the repo's solutions store (default docs/solutions/), shortlist notes by frontmatter (tags, area, title) and file paths the task will touch, read only the few relevant notes in full, cite and apply them, and update recurrence fields when the same situation repeats. Use this skill at the start of any non-trivial task in an area with captured lessons, when the user says "lần sau nhớ", "nhớ bài học", "check the notes", "đã gặp vụ này chưa", "have we seen this before", or when a problem feels familiar; also use it when the user asks to review or clean up the notes store. Skip it when no solutions store exists, for trivial one-line changes, and never bulk-read every note into context.