Use after work begun with recall, or any work requiring more than one tool call or non-trivial thought. Use immediately for explicit save requests ("remember this", "save that", "note for next time"), and the moment a review, failing check, or user correction confirms a lesson; capture it before applying the fix. Also use at session end when a presented conclusion, design, or finding was later overturned or corrected. Use when a specific approach is confirmed: the user praises a reusable behavior, or an uncertain choice succeeds with observable evidence. This preserves lessons for future recall.
Use when operating or configuring the sweeper background job.
Use when operating or configuring the sweeper background job.
Use when the user asks you to take a task end-to-end. Triggers on the explicit slash form `/please <ask>` and on natural-language phrasings of the same intent: "please do X", "please work through X", "please take care of X", "work through X end-to-end", "take this end-to-end", "drive X to completion", "see this through". An `<ask>` argument is required — without one, ask the user a single clarifying question and wait. Do not fire on casual uses of "please" attached to a single trivial action ("please read this file", "please rename this var") — fire only when the user is handing over a multi-step piece of work to be carried end-to-end. The explicit slash form `/please <ask>` is an opt-in and always fires regardless of how trivial the ask looks — the user chose the workflow deliberately.
Use after any user request that might entail more than a single tool call or anything more than quick, shallow thinking. This surfaces relevant memories that are VITAL to recall for a good user experience and a greater chance at first-pass success for the user's request.
Executes a vault write handed off by another skill (recall, learn): composes the engram command from the provided fields, runs it, verifies the result, and reports the written note path. Requires a handoff — do not fire on your own judgment that something is worth remembering.
Use when you are about to dispatch a subagent and must decide its agent type, model, and effort level. Triggers on any delegation decision, and when you recognize a unit is too large for one focused agent and needs decomposition before dispatch.
Use after any user request that might entail more than a single tool call or anything more than quick, shallow thinking. This surfaces relevant memories that are VITAL to recall for a good user experience and a greater chance at first-pass success for the user's request.