What problem does it solve? Findings from debugging sessions, incident resolutions, and PR reviews are often lost because they are never written down, forcing teams to re-investigate the same problems. This Skill structures the capture of what was learned immediately after an investigation concludes. ## Core Features & Use Cases - Four-question capture framework: Records what is now proven (with scope and date), which prior belief was wrong, whether a procedure changed, and whether a check could have caught the issue. - Routed destinations: Directs each kind of learning to the right place — dated notes in wip/<workstream>/, procedure updates in .claude/skills/<name>/SKILL.md, cross-session memory, or executable checks in scripts/ or hooks. - In-place correction style: Wrong claims are struck through and corrected rather than deleted, preserving the reasoning that produced them. - Use Case: After root-causing why etcd snapshots went stale in a QA environment, run this Skill to write a dated note, correct the stale belief in the existing docs, and add a lint check so the failure recurs as a red test instead of a repeated outage. ## Quick Start Ask the assistant to capture what was just learned from the investigation and write it up as a dated knowledge base note.
