What problem does it solve? When debugging a recurring error or making an architecture decision, teams often re-derive solutions that were already found and documented. This Skill searches the project's markdown memory notes by symptom before acting, so prior solutions are reused instead of re-investigated or re-broken. ## Core Features & Use Cases - Symptom-ranked recall: Searches LOCAL, PROJECT, and USER memory scopes in one call using memgrep, with a plain-grep fallback when memgrep is unavailable. - Scope precedence handling: Resolves conflicting facts across scopes by preferring the more specific scope (LOCAL > PROJECT > USER). - Lesson-aware reading: Surfaces each note's linked lessons-learned sections so the reasoning behind a fact is understood, not just the fact itself. - Use Case: A recurring bash hang appears during a session. Before debugging, you recall the symptom ("every bash command hangs / stuck at password prompt") and immediately retrieve the prior note explaining the cause and fix. ## Quick Start Before debugging this recurring error, search the project memory notes for the exact symptom text and read the top matching notes.
