retrospective-codify

Codifying retrospective learnings means summarizing actionable insights from completed work into static rules or checklists. This workflow evaluates whether insights should become project guidelines, notes, or new skills to prevent repeating mistakes.

You should formalize lessons learned into project documentation when working with recurring workflows or repeated trial-and-error. Capturing these insights as codified rules prevents repeating mistakes and enables faster, more consistent execution in future tasks.

Updating CLAUDE.md with new guidelines involves summarizing actionable learnings from a finished task and translating them into structured entries. The process helps decide whether to update existing files, create new skills, or publish cross-project guidelines.

Creating new skills from user feedback involves summarizing actionable learnings and evaluating their reusability. You then decide whether to codify them as new skills, update existing ones, or document them as project rules for cross-project reuse.

Yes, you can use retrospective codification for cross-project workflow standardization by publishing guidelines to shared files like CLAUDE.md. This captures repeated trial-and-error insights and applies them as static rules or prompts across multiple recurring workflows.