Reflect

Use after delivery, review, or investigation. Turn what this session taught into guidance next session gets for free. A lesson is something surprising, retried, corrected by user, repeated enough to template, or a decision whose rationale would otherwise be re-derived. Use current-session evidence or evidence explicitly supplied by user; do not invent history.

1. Harvest

List every candidate lesson. Yield order: failures and diagnoses (wrong assumptions, killed checks, reversions), user corrections, repeated manual choreography, hard-won design decisions, and clarified/conflicting domain terms. Account for every failure and user correction: keep it or dismiss it explicitly. Capture evidence, recurrence trigger, and why it matters.

2. Classify

Give each lesson exactly one disposition:

• Skill edit — changes repeatable process. Search existing skills; update single skill owning process. If two fit, more specific owner wins.
• New skill — repeatable process no skill owns and has distinct trigger/leading verb. Prefer thin composition pointing to existing skills over restatement.
• Memory — durable user preference, private ephemeral project state, or agent bias. Keep private.
• Docs — durable domain language or source-derived explanation for maintainers.
• ADR — consequential hard-to-reverse decision with real alternatives and rationale.
• No-op — situational, stale, unverified, or already default behavior. State dismissal reason.