task-retrospective

To capture lessons learned and avoid repeating mistakes, create a dated retrospective file in the .context/retrospectives/ directory following a standardized template to structure What Went Well, What Could Be Improved, and Lessons Learned.

You should write a task retrospective after completing medium or complex tasks, experiencing surprising behavior, finishing long-running work, or resolving tricky debugging sessions to capture structured insights for future reference.

Structure a post-mortem for tricky debugging sessions by documenting What Went Well, What Could Be Improved, Lessons Learned, and Promotion Items using a standardized template stored in your project context directory.

Yes, task review documentation requires a .context/retrospectives/ directory to store dated retrospective files and a standardized template defined in the SKILL.md to properly structure your captured insights.

Yes, you can promote retrospective insights to permanent documentation by identifying Promotion Items during the task review and using context-maintenance workflows to transfer these learnings into your permanent project docs.

The best way to maintain context and prevent repeated work on long-running tasks is performing structured retrospectives that capture lessons learned and storing them in a dedicated retrospectives directory for future reference and learning.