Skip to content
Back to skills

Project Memory

ASecurity

Use to create and maintain durable cross-session project memory and the progress ledger, so long autonomous builds resume cleanly after compaction, restarts, or new sessions. Read it when starting work and update it as decisions and tasks land.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 7, 2026
developmentrustgitfrontend

Security analysis

A100/100

Scanned September 7, 2026

npx -y skills add martian56/claude-engineer --skill project-memory --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Memory?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Memory
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/martian56-project-memory/badge)](https://www.skillsdirectory.com/skills/martian56-project-memory)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-memory
description: Use to create and maintain durable cross-session project memory and the progress ledger, so long autonomous builds resume cleanly after compaction, restarts, or new sessions. Read it when starting work and update it as decisions and tasks land.
---

# Project Memory

**Announce at start:** "I'm using claude-engineer:project-memory to keep durable project state."

Long autonomous builds outlive a single context window. Memory lives in **files**, not your head.
The claude-engineer SessionStart hook auto-loads these at the start of every session.

## The state files (in `.claude-engineer/`)
- **`memory.md`** - durable project memory: key decisions (+ why), established conventions, the data model, open threads/risks, and "next action". The single source of truth for *why things are the way they are*.
- **`progress.md`** - the task ledger: each task with status (todo / doing / done), the commit/branch, and a one-line result. Append-only-ish; never delete history.
- **`current-phase.txt`** - one line naming the active phase (e.g. `Phase 2 - Frontend`).
- **`quality-gate-status.json`** - written by the project quality-gate runner; read by the commit gate. Do not hand-edit.

## Iron Law
**Trust the ledger and `git log` over your own recollection.** After compaction, re-read these files before acting. Never re-run a task `progress.md` marks done.

## When to update
- **After every task:** append a line to `progress.md`.
- **On every non-obvious decision:** add it to `memory.md` (mirror big ones into `docs/plan/decisions.md`).
- **On phase change:** update `current-phase.txt`.

## Initialize (Phase 0 / planning)
Create `.claude-engineer/` with seed `memory.md` (problem, stack, data model, decisions-so-far, next action), an empty `progress.md` ledger, and `current-phase.txt`. Add `.claude-engineer/quality-gate-status.json` to `.gitignore` (machine-generated); commit `memory.md`/`progress.md` so teammates and future sessions share them.

## Red flags - STOP
- Starting work without reading `memory.md` + `progress.md` first.
- A decision made in chat but never written down → write it now; chat is not durable.
- Re-deriving something already settled in `memory.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.