learn

Centralize project learnings by running the /learn command to consolidate and surface patterns across sessions in a local knowledge-management store. It groups recent entries by type so teams can recall past decisions and avoid repeating mistakes.

Yes, you can search past project learnings in the local store by running /learn search <query>. This surfaces matching entries and historical patterns from your centralized knowledge base to guide current decisions.

Prune stale or outdated knowledge-management entries by executing the /learn prune command. This removes obsolete project learnings from your local store, keeping the knowledge base relevant and accurate for future reviews.

Export project learnings for team sharing by using the /learn export command. This extracts consolidated insights and historical patterns from your local store into a shareable format for quick knowledge distribution.

No, the /learn CLI workflow operates on local learning stores without requiring external dependencies. It functions independently to review, search, prune, and export project learnings directly within your environment.

You need a centralized project learnings manager when your team struggles to recall past patterns and decisions across sessions. It proactively surfaces historical insights to guide better decision-making and prevent repeating previous mistakes.