manage-lessons

To capture lessons learned from errors across projects, use the from-error operation to document the issue with component, category, and detail metadata. This creates a global note that remains accessible across all plans and components for future reuse.

The best way to organize global lessons learned is by storing them as Markdown files with structured metadata. You can query these notes by component, category, or applied status, and archive outdated entries to support long-term knowledge retention without cluttering active results.

You can query existing lessons by component or applied status using the get and list operations. These scripts-based commands filter your global Markdown metadata storage, returning specific notes so you can track improvements and verify if a lesson has already been applied.

Yes, you can update lesson metadata after creation using the update operation. This allows you to modify the component, category, title, or detail of a global note, ensuring your shared knowledge stays accurate as project requirements evolve over time.

Archiving lessons does not delete them but supports long-term knowledge retention by moving them out of active global scope queries. You can still retrieve archived notes if needed, keeping your active list uncluttered while preserving institutional knowledge.