development-memory

Capture project knowledge checkpoints and recall past work via fast_search.

3|Updated May 29, 2026
One-click install
npx skills add https://github.com/anortham/miller --skill development-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-memory
Source: https://github.com/anortham/miller/tree/main/.claude/skills/development-memory
Command: npx skills add https://github.com/anortham/miller --skill development-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill builds a persistent project knowledge base through systematic checkpoints and recalls past work to reduce repeat effort.

Core Features & Use Cases

  • Proactive checkpoints after significant work
  • Recall past work before starting similar tasks
  • Searchable knowledge base with fast recall

Quick Start

After finishing a bug fix, call checkpoint with a description, then recall before starting related work.

Frequently Asked Questions about development-memory

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

FAQPage Schema
How do I capture and store knowledge from bug fixes and architectural decisions?

Checkpointing systematically records project decisions and solutions into a searchable knowledge base. Call checkpoint after completing significant work—bug fixes, architectural choices, or complex problem-solving—with a description. This prevents repeating the same debugging effort and makes past solutions immediately retrievable.

Can I search and recall past work before starting a new task?

Yes. The recall workflow lets you query the knowledge base using fast_search before tackling related work. This retrieves past checkpoints, solutions, and decisions so you avoid duplicating effort and apply previously learned patterns to similar problems.

What's the best way to prevent knowledge loss during development?

Proactive checkpointing after significant work creates a persistent, taggable knowledge base accessible via fast search. Systematic capture at key moments—after bug fixes, architectural decisions, and complex problem-solving—ensures solutions and context are recorded before details fade.

How does checkpoint capture work with git context?

Checkpointing captures git context in under 50ms, recording the current state alongside your description. This ties knowledge directly to code changes, making it fast to snapshot decisions at the moment they're made and correlate past solutions to specific code states.

Can I tag and organize checkpoints in the knowledge base?

Yes. Checkpoints are taggable and searchable through the knowledge base, allowing you to organize captured work by topic, component, or decision type. This structure makes retrieval faster and helps surface related past work when investigating similar code areas.