reflectlisted

# Reflect Turn what this session actually established into a dated entry in `docs/LEARNINGS.md`. Nothing is written before the user confirms the proposed text. This skill is the manual trigger for a duty the plugin already carries: `buzz-team-communication` requires `docs/LEARNINGS.md` to be updated after any significant work session. Reflect is not a second memory system. It writes to that one file, in that file's language, under its append-only rule. ## When to run it The user asks for it. There is no hook, no background mode, and no configuration file. A good moment is the end of a work session, after the result has been published and while the reasons for each decision are still in the conversation. ## What qualifies as a learning Keep the bar high. `docs/LEARNINGS.md` is read by every future agent on the project, so every entry costs someone's attention. Write it down when the session produced: - **A verified fact** that was not obvious from the code, and that cost effort to establish. "The listener reloads its allowlist every two seconds, so a restart is unnecessary." - **A decision with its reason.** The decision alone ages badly; the reason is what lets the next agent tell whether it still holds. - **A trap.** Something that looked right, was wrong, and would catch the next person the same way. - **A correction.** An earlier entry, or an earlier belief, that this session disproved. - **A regression and its cause**, once the cause is actually known.