lessons-learned

Lessons learned notes are captured using a two-file structure: LessonsLearned.GLOBAL.md for global tooling guidance and LessonsLearned.md for per-user workspace knowledge, preventing repeated mistakes across skills.

Organize knowledge management feedback by categorizing entries into Codebase or Process/Model categories, applying promotion rules to move validated lessons into SKILL.md when they require permanent workflow guidance.

A two-file structure for feedback loops is needed when coordinating cross-skill lessons across global and local environments, separating global tooling guidelines from workspace-specific knowledge to maintain a clean knowledge base.

Prevent duplicate knowledge management entries by running deduplication checks during atomic promotions, ensuring that new lessons learned are validated against existing notes before being added to the evolving knowledge base.

Yes, per-user workspace notes can be promoted to global skill documentation through atomic promotions, moving validated entries from LessonsLearned.md into SKILL.md or LessonsLearned.GLOBAL.md to share guidance across teams.

Managing lessons learned notes requires strict adherence to the two-file pattern and category tagging; without atomic promotions and deduplication checks, the knowledge base across different agents can become cluttered or inconsistent.