remnic-memory-workflow

## When to use Use this skill as the default playbook whenever an agent picks up a task that could benefit from prior context, or when the user explicitly asks the agent to remember or recall something. It is the umbrella workflow — individual skills (`remnic-recall`, `remnic-remember`, `remnic-search`, `remnic-entities`, `remnic-status`) implement the detailed steps. Triggers: - The user opens a new task, ticket, or branch. - The user says "what do you know about X", "have we talked about Y before", "remind me of Z". - The user asks the agent to save a preference, decision, or fact. - A long-running turn produces a durable outcome worth capturing. ## Inputs - Current user request (natural language). - Optional: active project path, ticket number, branch name. - Optional: topic keywords surfaced earlier in the session. ## Procedure 1. **Recall first.** Call `remnic_recall` with a concise natural-language query derived from the user's request. Pull 3–8 results. Skim them for anything relevant. 2. **Mention relevant memories briefly** to the user if they materially change the plan, otherwise quietly use them as context. 3. **Observe during work.** For significant tool outputs (file edits, command exits, test results) call `remnic_observe` so Remnic can keep its ambient context fresh. 4. **Deep search when needed.** If `remnic_recall` misses something the user insists exists, call `remnic_lcm_search` with a more literal phrase. 5. **Browse entities.** When the user refere...