frmoretto

Memory Trail — AI skill for Claude Code

AI community

Decision memory and session logging for AI-assisted development.

How to install Memory Trail

This entry records only its repository, not the path inside it, so there is no exact command to give. Open frmoretto/memory-trail and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Memory Trail does

Decision memory and session logging for AI-assisted development. Track WHY decisions are made, not just WHAT changed. Works with Claude, Cursor, Roo Code, and other AI coding assistants.

Alternatives in AI

  • Paul — Plan-Apply-Unify Loop — Structured AI-assisted development for Claude Code 1.2k ★
  • Learning Opportunities — A Claude Code skill for deliberate skill development during AI-assisted coding 793 ★
  • LaTeX Document Skill — Universal LaTeX document skill for Claude Code: 27 templates, 27 scripts, 26 reference guides 725 ★

README

Memory Trail v1.1

**Open-source decision memory and session logging for AI-assisted development.**

[![License: CC BY 4.0](https://img.shields.io/badge/License-CC_BY_4.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/)

*"Checkpoints track WHAT changed. Memory Trail tracks WHY."*


The Problem

AI coding assistants make decisions but don't remember why. Each session starts fresh.

Session 1: "Should I cache images locally?" → Agent caches images
Session 2: "Should I cache images locally?" → Agent caches images again
Session 3: User discovers TOS violation, deletes cache
Session 4: "Should I cache images locally?" → Agent caches images (forgot again)

The agent isn't malfunctioning. It simply has no memory of past decisions.

**Git tracks WHAT changed.** Nobody tracks WHY.

Tool Tracks
Git Code diffs — WHAT changed
Changelog Release notes — WHAT shipped
Memory Trail Decision rationale — WHY it changed

What Is Memory Trail?

Memory Trail is an **open-source persistence layer** for AI-assisted development.

  • Memory — Decisions persist across sessions
  • Trail — Follow the breadcrumbs back to understand WHY

Core Components

Component Purpose Format
Decision Memory Architectural constraints agents must follow docs/DECISION_MEMORY.md
Confidence Protocol Structured uncertainty signaling with risk adjustments Agent behavior
STOP Triggers Hard stops for dangerous operations Agent behavior
Session Logs Per-task action traces docs/sessions/SES-YYYY-MM-DD-NNN.md

With Memory Trail

Session 1: Agent checks Decision Memory → [DEC-001] Use PostgreSQL
Session 2: Agent checks Decision Memory → [DEC-001] Use PostgreSQL
Session 3: Agent checks Decision Memory → [DEC-001] Use PostgreSQL
(Constraint persists across all sessions)

Quick Start

Option 1: Claude Skills (claud