memory-update

Capture project decisions into MEMORY.md with date-stamped entries.

12|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill memory-update-space-dinosaurs
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: memory-update
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/memory-update
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill memory-update-space-dinosaurs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically documents critical project decisions by appending verifiable memories to MEMORY.md, ensuring new engineers stay aligned with architectural choices and tradeoffs.

Core Features & Use Cases

  • Spawns a background memory worker to write concise, verified memory entries without blocking user workflows.
  • Validates that MEMORY.md exists and warns about orphan memory files from older tool versions.
  • Maintains a simple, auditable log of decisions for onboarding, audits, and knowledge transfer.

Quick Start

Replace the placeholder with a real decision context and trigger the memory update command.

Frequently Asked Questions about memory-update

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

FAQPage Schema
How do I automatically log engineering decisions to a markdown file?โ–ผ

The memory update process captures architectural decisions and tradeoffs by appending verifiable, date-stamped entries to MEMORY.md, ensuring future contributors understand the rationale behind project direction changes.

What is the best way to maintain an auditable log of architectural tradeoffs for onboarding?โ–ผ

You log architectural decisions by running a memory update command that spawns a background worker to append verified, date-stamped entries to MEMORY.md at your current working directory without interrupting user workflows.

Can I write project memories in the background without blocking my current workflow?โ–ผ

Yes, the memory worker operates in the background, allowing you to continue engineering tasks while it validates the memory file and writes date-stamped decision logs to MEMORY.md asynchronously.

Does the memory logging tool warn about orphan memory files from older tool versions?โ–ผ

Yes, the tool checks for orphan memory files from older tool versions and warns you if they are present, ensuring your engineering memory log remains clean and auditable.

How do I document policy changes and tradeoffs that affect project direction?โ–ผ

To document policy changes, you provide a real decision context and trigger the memory update command, which spawns a background worker to append a verified, date-stamped memory entry to MEMORY.md.