Capturing Learning from Completed Work

Capturing learning from completed work involves documenting key decisions, failed approaches, and non-obvious issues discovered during development. This Skill guides you through a structured retrospective after significant features, bug fixes, or debugging sessions, producing searchable summaries linked to relevant code changes so your team can reference solutions without re-investigating similar problems.

Use retrospectives after significant features, substantial bug fixes, lengthy debugging sessions, time overruns beyond initial estimates, or situations where multiple approaches were discarded. These moments carry the most valuable context and lessons; capturing them systematically while fresh prevents knowledge loss as engineers move to the next task.

Document what was accomplished, key decisions and their rationale, approaches tried and why they failed, non-obvious issues discovered and how they were solved, and actual time spent versus initial estimates with explanations for significant variances. This structured capture ensures decisions and discarded solutions become searchable team knowledge.

Systematic documentation creates a searchable knowledge repository where insights, failed approaches, and subtle issues from completed work are preserved and shared across the team. This prevents repeated mistakes, accelerates future development, and ensures that valuable lessons discovered during debugging or complex features remain accessible after engineers move on.

Yes. This Skill implements a systematic retrospective workflow that produces structured, searchable summaries and links to relevant code changes, designed to integrate with existing collaboration commands so learning capture fits naturally into your team's development process without additional overhead.