capture-learnings

Capture learnings by running a flow that extracts actionable insights from a coding session, such as bug fixes and architectural decisions, and appends them as a dated entry to your project's learnings.md file.

Maintaining a development knowledge base involves appending formatted entries to learnings.md, creating a lasting, searchable record of bugs fixed, gotchas, and config discoveries under dated sections.

You need to document learnings in a learnings.md file during active coding sessions and after major work to preserve institutional memory and enable targeted improvements across existing skills.

Yes, you can cross-reference captured learnings against existing skills to propose targeted improvements by automatically comparing your session's insights with your current skill configurations.

Capturing session learnings requires no external dependencies, operating independently to format entries and write them directly to your project's local learnings.md file.

Formatting retrospective entries under dated sections in learnings.md ensures a consistent, searchable record of institutional memory, allowing quick reference of what was learned during specific development periods.