Capturing Learning from Completed Work

What problem does it solves? Valuable lessons, discarded approaches, and subtle issues from completed work are often lost as engineers move to the next task. This Skill provides a systematic retrospective workflow to capture critical learning while context is fresh, preserving knowledge and preventing repeated mistakes.

Core Features & Use Cases

• Structured Retrospective: Guides capturing key decisions, failed approaches, issues discovered, and time spent vs. estimates.
• Combats Rationalizations: Explicitly addresses common excuses for skipping learning capture (e.g., "too tired," "memory fades"), ensuring discipline.
• Knowledge Repository: Ensures insights are documented, searchable, and shared across the team, preventing repeated mistakes and accelerating future development.
• Use Case: After a multi-hour debugging session, use this Skill to document the root cause, discarded solutions, and the final fix, ensuring that future team members can quickly find solutions to similar problems without re-investigating.

Quick Start

After completing significant work or a complex debugging session:

/summarise

The Skill will prompt you to document:

- What was accomplished

- Key decisions made (and why)

- Approaches that were tried and discarded (and why they didn't work)

- Non-obvious issues discovered (and how they were solved)

- Time spent vs. initial estimate (if significantly different, why?)