revisit
The session retrospective: every mistake gets classified and becomes a written rule, so the same failure can't ship twice.
What it is
The retrospective that closes a working session: read the session log, classify each mistake, and write the rule that would have prevented it. Metrics and ideas files keep score across sessions. The premise is that a mistake without a written rule will recur.
Why
A mistake that only gets fixed will happen again; a mistake that becomes a written rule can't ship the same way twice. The retrospective is the step that turns corrections into system.
How I use it
It runs on demand at session end and automatically on session close. The output feeds a promotion pipeline: lessons that recur across sessions get promoted from the log into the standing instructions every future session loads.
Get it
The whole method is downloadable and adaptable — skills/revisit/SKILL.md inside the zip. The habit transfers without tooling: end sessions by writing the rule, not just the summary.
Connected
This thread is scoped to revisit. Opening another node starts a new one.
Ask this node