# Project Memory

> Use when maintaining project state, decisions, evidence, or a handoff that must survive a new session.

- Skill: `jukrap/project-memory` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jukrap/project-memory`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jukrap/project-memory/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jukrap (https://skillmd.com/u/jukrap)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jukrap/project-memory

---


# Project Memory

Use the project's existing record entrypoint, such as CURRENT.md, for the active objective, constraints, next action, and links. Read only relevant records, narrowing by repository, topic, month, kind, or path where supported before expanding. Ordinary edits do not require a new worklog.

Record meaningful milestones, decisions, important findings, blockers, and handoffs. Keep current reusable facts in topic knowledge and detailed evidence in dated worklogs, using monthly folders for the new layout. Preserve existing records, ownership, source locators, and local-only rules; distinguish intended contracts, implementation, configuration, and observed behavior.

Shared workspace records apply only to explicitly registered members. Confirm the selected repository before code or Git operations; record location alone does not select a code target. Records do not require Git.

Read `references/current-state.md` when updating current state or resuming work. Read `references/evidence-and-handoff.md` for detailed evidence, handoffs, or an optional independent DRAFT. The main task normally records its own work; it reviews delegated drafts before incorporation. Native host memory is optional; ordinary files are sufficient.