Close

One skill, four phases, in this order: LEARN, FIX, PROVE, REPORT.

Two failures, one fix. The first: you correct Claude all session, close the window, and next week it makes the same mistakes, because nothing wrote the lessons down. The second: the session ends with a nine-item list of things you now have to do. Remembering every loose end and handing them all back has moved the work sideways, not forward.

So the job is: bank what is worth keeping, finish every loose end you can, prove it, and hand back only what is genuinely theirs. Then say plainly whether anything is still open.

Only run LEARN on a session that went well

This skill turns what happened into standing instructions. On a bad session it writes the WRONG behaviour into memory, and every future session inherits it.

The test: would the user be happy for the next session to work the same way? If no, say so. Skip the banking in PHASE 1, still run FIX and PROVE, and say in the report that nothing was banked because the session was not one to learn from. Still run 1.4, the friction sweep. A bad session is where the friction is, and fixing its cause is the one lesson it does teach.

PHASE 1: LEARN. Bank what the session taught, and reject most of it.

1.1 Find where memory lives