retrieving-memory

Retrieves prior repository knowledgebfed by keyword to inform coding decisions.

26|3|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill retrieving-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrieving-memory
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/retrieving-memory
Command: npx skills add https://github.com/davidlee/spec-driver --skill retrieving-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents “probably/likely” assumptions and incorrect guidance in large codebases by forcing the agent to retrieve and cite relevant, source-of-truth memories before taking consequential actions.

Core Features & Use Cases

  • Contextual memory retrieval using scoped queries by expected file paths and command context to find the most relevant prior guidance.
  • Metadata narrowing and candidate inspection to efficiently shortlist memories, then inspect full details for accuracy.
  • Trust and staleness discipline by prioritizing severity/weight/scope specificity and highlighting verification state so conflicting cues are escalated instead of averaged.
  • Output citation requirement ensuring responses and plans cite memory IDs and their linked sources (and re-retrieve with tighter parameters if citations are missing).

Quick Start

Use retrieving-memory before making changes to a subsystem you have not touched this run by running a scoped memory query for the file paths you expect to edit and the command pipeline you plan to execute.

Frequently Asked Questions about retrieving-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to resolve conflicting code and documentation cues during debugging?

Resolve conflicting code and documentation cues by retrieving repository memories and inspecting full details via show/find commands. Conflicting cues are escalated based on verification state and metadata severity rather than averaged out, ensuring accurate guidance.

Why do I need to cite memory IDs and provenance before proceeding with codebase changes?

Find the right way to execute risky command pipelines by narrowing memory candidates with metadata like severity, weight, and scope specificity. Inspect full memory details to verify accuracy before proceeding with consequential actions.

When should I not rely on memory retrieval for spec-driven development?

Citing memory IDs and their linked provenance before proceeding ensures responses and plans are backed by verified sources. If citations are missing, the agent re-retrieves memories with tighter parameters to maintain citation discipline.

Can I use scoped querying to debug recurrent failures in unfamiliar subsystems?

Do not rely on memory retrieval without checking staleness awareness and verification state. If prior memories lack sufficient severity, weight, or scope specificity for your current file paths, escalate the conflicting cues instead of proceeding with outdated guidance.

Can I use scoped querying to debug recurrent failures in unfamiliar subsystems?

Use scoped querying to debug recurrent failures by running memory queries for expected file paths and command pipelines you plan to execute. This retrieves relevant prior guidance to answer right way here questions with confidence.