memex-retro

Save distilled development insights into persistent Zettelkasten memory cards.

139|41|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/iamtouchskyer/memex --skill memex-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memex-retro
Source: https://github.com/iamtouchskyer/memex/tree/main/skills/memex-retro
Command: npx skills add https://github.com/iamtouchskyer/memex --skill memex-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and preserve the key lessons learned during development tasks so future sessions and agents can recall prior decisions, fixes, and design insights instead of starting from scratch.

Core Features & Use Cases

  • Structured post-task retrospection that distills one atomic insight per note.
  • Fact hygiene and deduplication checks that make implicit context explicit and avoid duplicate cards.
  • Integrates with memex CLI or MCP tools to search, read, update, and write persistent Zettelkasten-style cards after coding, debugging, or architectural work.

Quick Start

After finishing the task, draft one atomic insight per card, perform fact-hygiene and search for existing cards, then write or update the memex cards using the memex tools.

Frequently Asked Questions about memex-retro

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

FAQPage Schema
How do I save atomic insights from a coding session into a Zettelkasten?

To save atomic insights into a Zettelkasten, you draft one distilled insight per note, perform fact-hygiene and deduplication checks, and then write or update persistent cards using memex CLI or MCP tools.

What is the best way to perform a post-task retrospective for development work?

The best way to perform a post-task retrospective is to distill one atomic insight per note from completed development tasks, ensuring fact-hygiene and searching for existing cards to avoid duplicates before writing to memex.

Do I need the memex CLI to record architectural decisions and debugging sessions?

You need either the memex CLI or MCP tools with memex_search, memex_read, and memex_write functions to record architectural decisions and debugging sessions into a persistent Zettelkasten memory.

Can I use MCP tools to write and update Zettelkasten cards for future sessions?

Yes, you can use MCP tools with memex_search, memex_read, and memex_write to search existing cards, read content, and write or update Zettelkasten cards while enforcing frontmatter preservation for future sessions.

How does fact-hygiene and deduplication work when saving retrospective notes?

Fact-hygiene makes implicit context explicit, while deduplication searches existing memex cards before writing to prevent duplicate notes, ensuring your retrospective memory remains clean and accurate.

Why should I preserve frontmatter when updating Zettelkasten memory cards?

You must preserve frontmatter when updating Zettelkasten memory cards to maintain the structural integrity and metadata of existing notes, ensuring future sessions can correctly parse and recall prior learnings.