context-memorylisted

# Context Memory Use this skill when you need durable knowledge that should survive beyond the current task. ## Why This Skill Exists Task files explain one work item. `context-memory` explains what should persist across work items and sessions. Use this skill when the information is bigger than one task, or when future work will benefit from remembering a non-obvious fact or decision. ## When To Use This Skill Use this skill when: - you need to search past project memory before making a decision - you discovered a non-obvious fact worth preserving across sessions - you want to record a durable decision so it is not re-opened casually - you need to update `.my-context/MEMORY.md` - you need to add or revise `.my-context/architecture/` notes or other memory docs Do not use this skill for active task notes or execution progress. Use `context-task` for that. ## Core Principle Project memory should preserve high-value context, not session chatter. Keep only information that will still matter when the current diff, current task, and current conversation are no longer open. ## Memory Search First Before making a structural change, reopening a prior decision, or writing a memory update, search existing memory first. If the `memory_search` tool is available (Pi with `pi-memory` extension), use it directly — it defaults to the current project when `YISHAN_PROJECT_ID` is set. Fallback CLI command (when running outside Pi): ```bash yishan memory search --output json --pr