memory-recall

To retrieve historical context, the Skill resolves the memory bridge using your project directory and state file, issuing a recall query to return source-aware summaries of relevant long-term memories.

A memory bridge is a workflow binding mechanism that identifies the path to stored memories. It controls recall scope and provenance using inputs like the project directory, state file, and top-k results.

You get concise summaries of past decisions by executing a recall search against the memory store. The Skill ranks results by relevance and produces curated, source-tagged summaries for quick traceability.

Yes, you can control the number of memories returned during a recall query by configuring the top-k input parameter within the memory bridge workflow, which directly limits the ranked results.

When a recall search finds no relevant long-term memories, the Skill enforces output discipline by returning a clear fallback message stating no relevant memories were found, ensuring no hallucinated context.

Yes, the memory recall process provides traceability to original session data by generating source-aware summaries. These curated outputs include source tags for quick traceability back to the original memories.