capturing-memory

Create structured memory records with narrow memory_type during phase wrap-up.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capturing-memory prevents valuable decisions, invariants, workflows, and sharp-edge lessons from getting lost in transient work notes, so future agents don’t repeat the same research or stumble into the same pitfalls.

Core Features & Use Cases

  • Durable memory capture: Records repeatable guidance whenever you discover durable facts, constraints, invariants, or “how we do X here” patterns.
  • Workflow and checklist reuse: Helps you persist newly created recurring workflows/checklists so they can be invoked again later.
  • Rework prevention: Stores non-ADR/SPEC decisions that would otherwise cause future rework, plus footguns and non-obvious dependencies.
  • Phase/delta wrap-up discipline: Enforces scanning notes, phase sheets, audit findings, and fresh gotchas before treating anything as wrapped.
  • Structured memory taxonomy: Uses the narrowest memory_type to keep retrieval precise (fact, pattern, system, concept, signpost, thread), with explicit confidence calibration and optional provenance.

Quick Start

Use capturing-memory at phase or delta wrap-up to scan current notes for durable guidance, then create a memory record with the narrowest memory_type using spec-driver create memory "..." --type <concept|fact|pattern|signpost|system|thread> --summary "..." --tag ....

Frequently Asked Questions about capturing-memory

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

FAQPage Schema
How do I preserve durable knowledge management decisions for future agents?

Preserve durable knowledge management decisions by capturing invariants, workflows, and sharp-edge guidance in structured memory records. This prevents future agents from repeating research or stumbling into known pitfalls during phase wrap-up.

What is the best way to prevent agent rework in spec-driven development?

Prevent agent rework in spec-driven development by scanning notes, phase sheets, and audit findings for durable items during delta wrap-up. Store non-ADR decisions and footguns as structured memory records to avoid rediscovery.

How do I capture agentic memory using a structured memory taxonomy?

Capture agentic memory by selecting the narrowest memory_type—such as fact, pattern, system, concept, signpost, or thread—to ensure precise retrieval. Apply confidence calibration and optional provenance when creating the structured record.

When do I need to capture workflow and checklist reuse patterns?

Capture workflow and checklist reuse patterns whenever you discover newly created recurring workflows during phase or delta wrap-up. Persisting these durable items ensures they can be invoked again by future agents without rework.

Does capturing-memory require any dependencies to manage invariant guidance?

Capturing-memory requires no external dependencies to manage invariant guidance. It operates independently to scan scratch work and fresh gotchas, resolving links and sanity-checking surfacing via list queries during wrap-up.

What are the limitations of relying on transient work notes for knowledge retrieval?

Transient work notes limit knowledge retrieval because valuable decisions and non-obvious dependencies get lost outside the current conversational context. Without structured memory capture, future agents face repeated research and operational pitfalls.