lessons-learned

To record project-specific lessons learned, you add high-value, anti-vibe learnings after significant errors are detected. The system applies quality filters to exclude generic clean-code or syntax issues, ensuring only non-obvious mistake patterns are stored to prevent future repeats.

Managing and pruning obsolete knowledge involves listing current lessons, checking their relevance, and safely removing outdated entries. This ensures the knowledge base remains concise and effective for preventing recurring mistakes across future coding sessions.

Quality filtering for adding new lessons learned works by rejecting syntax errors, already-covered issues, and generic clean-code advice. It strictly enforces recording only high-value, anti-vibe learnings that address non-obvious mistake patterns to maintain a focused knowledge base.

Yes, you can promote eligible lessons learned into broader, reusable senior principles. This process escalates specific project knowledge into a general guidance file, allowing the team to apply validated anti-pattern prevention across multiple projects.

Yes, the lessons learned tool works with different project layouts by automatically detecting the project layout structure. It then writes knowledge updates to the correct knowledge storage location based on this detected configuration.

You should not use a lessons learned knowledge management approach for recording syntax errors, already-covered issues, or generic clean-code advice. The system is designed exclusively for capturing non-obvious, costly mistake patterns to prevent their recurrence.