record-memory

Route completed change units into durable memory entries under docs/superpowers/memory.

5|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/LanternCX/Agent --skill record-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: record-memory
Source: https://github.com/LanternCX/Agent/tree/main/skill/record-memory
Command: npx skills add https://github.com/LanternCX/Agent --skill record-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to recording durable, reviewable changes as memory entries, ensuring important decisions and changes are preserved for future reference.

Core Features & Use Cases

  • Route completed work units into memory entries under docs/superpowers/memory/ with clear Type, Date, and Entry Template references.
  • Enforce entry discipline by linking to an ENTRY.md template and organizing entries by month.
  • Support discovery and consistency by guiding when to bootstrap or use existing types, so future work can be traced and understood.

Quick Start

Write a memory entry for the finished change unit using the docs/superpowers/memory template.

Frequently Asked Questions about record-memory

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

FAQPage Schema
How do I record completed work units as durable memory entries in a repository?▼

You record memory entries by routing completed change units into the repository under docs/superpowers/memory using an ENTRY.md template, organizing them into a monthly bucket structure for future reference.

What is the structure for archiving change units into documentation memory?▼

Archiving change units into documentation memory requires creating entries under docs/superpowers/memory, applying a proper ENTRY.md template with clear Type, Date, and Entry Template references within a monthly bucket structure.

When should I bootstrap a new memory type versus using an existing template?▼

Bootstrap a new memory type when a completed change unit has a clear goal requiring a distinct archival category, otherwise use existing templates to support discovery and consistency for future tracing.

Can I use custom templates for recording memory entries across different change types?▼

Yes, you can use templates for recording memory entries across types, as the process supports applying a proper ENTRY.md template when a single change unit is eligible for archival memory across various formats.

What is the best way to organize repository documentation for completed change units?▼

The best way to organize documentation for completed change units is enforcing entry discipline by linking to an ENTRY.md template and organizing entries by month under the docs/superpowers/memory directory.

What happens if a change unit lacks a clear goal for memory recording?▼

If a change unit lacks a clear goal, it does not meet the eligibility criteria for archival memory recording, as the process applies only when a single change unit has a clear goal for durable entry creation.