Project Memory

Project Memory Skill

Use this skill when the user wants to preserve, recover, migrate, or audit long-running project or research context across chat loss, model changes, tool handoffs, or multi-session work.

The skill separates current truth, plans, decisions, evidence, hypotheses, human summaries, and recovery checkpoints so that no single chat transcript becomes the source of truth.

When to use

Use this skill when the user asks to:

• start a new project and set up structured memory from scratch
• introduce structured memory into an existing project with accumulated context
• resume work after a lost or interrupted chat
• create a durable project memory or research log
• migrate context from one model, agent, workspace, or repository to another
• update project docs after new work, decisions, research, experiments, or failures
• produce a handoff brief for a human or another model
• distinguish confirmed facts from hypotheses, plans, and unresolved questions
• audit whether a project has enough continuity documentation
• manage a research paper, thesis, publication, or traceability-heavy project: track literature, connect findings to hypotheses, log figures and tables with their data sources

Do not use this skill as a replacement for domain expertise, citations, or source verification. It is a continuity and documentation-routing skill.

Operating assumption

The human usually does not write memory files directly. The AI agent is responsible for updating the project memory during the chat or coding session.

Do not rely on tool-internal or session-local memory as the canonical source of truth. Treat repository files as the durable, shared memory layer across Codex, Claude Code, and future tools.

Core principle

Capture broadly. Promote narrowly.

Do not let hypotheses, plans, or recovery notes silently become truth.

Routed memory rule

Project memory is not a full-file synchronization system.

Do not read or update every project-memory file on every run. Do not treat the file list or read order as a checklist.

Each piece of information should go to its canonical home. Update only the files whose canonical responsibility changed.

Most work sessions should update only 1-3 files. Larger updates are appropriate only during major transitions, such as phase changes, major hypothesis confirmation or rejection, architecture or approach changes, release checkpoints, or large migrations.

Before editing memory files, produce a short update plan stating:

• which files will be updated
• why each file needs an update
• which relevant files will not be touched

For a small, obvious one-file update, a one-sentence plan is enough. If you notice you are about to edit memory files without an update plan, stop and produce the plan first.

When one piece of information seems to belong in multiple files, choose one canonical home according to DOCS_GUIDE.md and CONTEXT_MANIFEST.md. Other files may reference the canonical entry, but should not duplicate the full details.

Read scope rule

Start with CONTEXT_MANIFEST.md when present.

Do not preemptively read the full memory set. Use the read order as a priority order, not as a checklist.

Before reading additional memory files, identify which files are relevant to the current task. For non-trivial work, briefly state which memory files will be read and which relevant files will not be read.

Conversation capture rule

During a work session, do not wait for the human to explicitly ask for logging.

Do not write to canonical memory files at the first appearance of an idea. Treat new hypotheses, decisions, observations, blockers, risks, and next actions as capture candidates until they stabilize. Keep capture candidates silently during the current session. Do not announce every candidate or repeatedly say that it is being held for later.

Write capture candidates to memory when the topic changes, the discussion reaches a conclusion, the session is ending or may be interrupted, the human explicitly asks to record something, or a decision, result, blocker, or next action becomes clear enough to preserve. After writing, briefly report what was recorded and where.

Capture only material that changes project memory. Do not summarize routine conversation, temporary phrasing, or early ideas that are still being refined.

Use RECOVERY_NOTES.md only as a short resume pointer. Do not make it the source of truth.

Profile and customization rule

project-memory is a skeleton, not a fixed operating system. Customize the profile, capture trigger strength, review cadence, archive policy, and tool-facing instructions to fit the project.

When initializing an empty workspace or adopting an existing project, recommend the smallest sufficient profile before writing memory files:

• light: small personal project, short-lived work, or minimal continuity
• standard: normal coding, writing, or product work with decisions and next actions
• research: experiments, evidence, hypotheses, repeated investigation, or debugging loops
• academic: literature, figures, tables, thesis, paper, provenance, or publication-grade traceability workflow

Recommend a capture trigger strength alongside the profile:

• light: record only explicit requests, session-end checkpoints, and major decisions
• standard: record topic-boundary decisions, next actions, blockers, and direction changes
• research: also record hypotheses, observations, failed attempts, and evidence changes
• academic: also record literature, methods, figures, tables, visual assets, provenance, and publication-grade traceability

Do not default to the largest profile or strongest capture trigger just to be safe. Use the lightest setup that preserves the project's real continuity needs.

Language behavior

Communicate with the user in the user's language by default.

Preserve the repository's dominant language for canonical docs and file names unless the user explicitly asks to change that policy.

If the repository language is unclear or mixed, confirm the canonical documentation language once before writing or translating structured memory files.

If chat language and doc language differ, explain in the chat language and keep the canonical docs in the chosen documentation language.

Route information by status:

| Information type | Canonical file | | --- | --- | | Confirmed current state | CURRENT_STATE.md | | Future intended work | ROADMAP.md | | Decisions and rationale | DECISION_LOG.md | | Research observations, experiments, evidence, results | RESEARCH_LOG.md when present; otherwise route direction-changing findings to DECISION_LOG.md and speculative observations to HYPOTHESIS_LAB.md | | Unverified ideas and speculative explanations | HYPOTHESIS_LAB.md | | Human-facing orientation summary | HUMAN_BRIEF.md when present | | Fast session resume checkpoint | RECOVERY_NOTES.md | | Compact combined history for the light profile | LOGBOOK.md | | Prior work, references, and their relevance (academic profile) | LITERATURE_NOTES.md | | Figures, tables, and visual outputs (academic profile) | FIGURES_LOG.md | | File roles, read order, ignore rules | CONTEXT_MANIFEST.md and DOCS_GUIDE.md |

Canonical memory rule

The canonical memory lives in version-controlled markdown files in the repository. Tool-specific memory features may help execution, but they must not be treated as the only source of truth.

In an existing project, never overwrite or delete existing project files without explicit user approval. Treat existing same-name files such as README.md, ROADMAP.md, DECISION_LOG.md, AGENTS.md, or CLAUDE.md as user-owned. If a project-memory template path collides with an existing file, place project-memory files under a non-conflicting directory such as memory/ or project-memory/, or record the chosen canonical locations in CONTEXT_MANIFEST.md.

Use:

• README.md as the entry point in a new memory workspace; in an existing project, keep the project README user-owned and use CONTEXT_MANIFEST.md to declare canonical memory locations
• CURRENT_STATE.md for current trusted assumptions
• ROADMAP.md for future intended work
• DECISION_LOG.md for adopted, rejected, or deferred decisions
• RESEARCH_LOG.md for tests, investigation, observations, and evidence when the selected profile includes it
• HYPOTHESIS_LAB.md for unverified ideas and emerging hypotheses
• HUMAN_BRIEF.md for fast human orientation when the selected profile includes it
• LOGBOOK.md for compact combined decisions, observations, hypotheses, and notes in the light profile
• RECOVERY_NOTES.md for restart checkpoints

If the repository also uses AGENTS.md, CLAUDE.md, or similar tool-facing guidance, keep those files short and point them to these canonical docs instead of duplicating project memory there.

Default read order

When resuming or migrating a project, read in this order unless CONTEXT_MANIFEST.md says otherwise:

This is a priority order for orientation, not a checklist to exhaust on every run. Read only as far as needed to route the current task safely.

1. CONTEXT_MANIFEST.md
2. latest entry in RECOVERY_NOTES.md
3. HUMAN_BRIEF.md when present, or LOGBOOK.md in the light profile
4. CURRENT_STATE.md
5. ROADMAP.md
6. latest relevant entries in DECISION_LOG.md
7. latest relevant entries in RESEARCH_LOG.md when present
8. HYPOTHESIS_LAB.md
9. DOCS_GUIDE.md when routing or updating docs is unclear

If CONTEXT_MANIFEST.md is missing, use the default read order above and recommend creating one.

Ignore rules

Before reading a repository or workspace, avoid obvious noise unless the user specifically asks for it:

• .git/, .hg/, .svn/
• .cache/, cache/, tmp/, .tmp/, __pycache__/
• generated logs unless the task is log analysis: logs/, *.log, *.jsonl
• build artifacts: dist/, build/, .next/, target/, node_modules/
• generated exports or run folders
• private data folders unless the user explicitly asks and access is appropriate

Use .contextignore if present. If a workspace has many generated files and no ignore policy, recommend adding one.

Update routing rules

When updating memory, first classify the new material.

Write to CURRENT_STATE.md when

• a fact, constraint, behavior, or rule is currently true
• a prior truth has changed or been retired
• future readers should rely on it without reconstructing history

Do not place untested claims here. If the claim is inferred but not verified, put it in HYPOTHESIS_LAB.md, or in RESEARCH_LOG.md with uncertainty when that file exists.

Write to ROADMAP.md when

• a future task, milestone, priority, or blocker changes
• something moves from idea to planned work
• something is deferred or dropped from near-term execution

A roadmap item is intent, not proof.

Write to DECISION_LOG.md when

• a meaningful choice is made
• alternatives were considered
• a failure or discovery changes direction
• future readers may ask “why did we do this?”

Each decision should include context, alternatives, rationale, risks, and revisit conditions.

Write to RESEARCH_LOG.md when present

• an experiment, investigation, test, literature review, source check, or observation happened
• evidence changed confidence in a hypothesis
• a null result or failed attempt matters

Keep methods, inputs, results, interpretation, confidence, and limitations together.

If RESEARCH_LOG.md is not in the selected profile, record direction-changing findings in DECISION_LOG.md and keep still-speculative observations in HYPOTHESIS_LAB.md.

Write to HYPOTHESIS_LAB.md when

• an idea is plausible but not confirmed
• a hunch, possible mechanism, or experiment proposal should be preserved
• something should be tested before being promoted
• the user expresses a new idea, discomfort, possibility, half-formed thought, or question worth revisiting

Structure HYPOTHESIS_LAB.md into:

Raw sparks

Low-commitment captures. These may be vague, incomplete, or speculative.

Working hypotheses

Ideas that have recurring relevance, clearer structure, or a defined next step.

Do not require the human to explicitly ask for logging. Prefer over-capturing in HYPOTHESIS_LAB.md over losing potentially valuable ideas.

Clean up HYPOTHESIS_LAB.md

Capture broadly. Delete cautiously.

Do not silently delete hypotheses or raw sparks from HYPOTHESIS_LAB.md.

When cleanup is useful, produce a review list first and group candidates by suggested action:

• merge
• promote
• link to evidence
• mark as dropped
• delete

The human must approve deletions and major merges before files are modified.

Raw sparks may be deleted after approval. Working hypotheses should usually be marked as dropped with a short reason rather than erased.

Write to HUMAN_BRIEF.md when

• a human needs a fast orientation to decide what to do
• the current goal, main blocker, main risk, or next decision changes
• the project should be explainable without reading all logs

Review HUMAN_BRIEF.md when any of the following occur, and update it only if the human-facing picture changed:

• a DECISION_LOG.md entry changes direction, priority, risk, tracked threads, or required human decisions
• a blocker is added, removed, or reprioritized in ROADMAP.md
• a hypothesis is promoted to CURRENT_STATE.md
• a RESEARCH_LOG.md entry changes confidence in a key assumption, when that file exists
• a RECOVERY_NOTES.md checkpoint changes the current goal, main blocker, next decision, or tracked thread status
• two or more parallel threads are active or paused and a human needs the current split

When updating, keep HUMAN_BRIEF.md short. It should summarize what matters for human judgment, not duplicate proof, history, or detailed methods.

At the top, maintain ## Tracked threads so parallel work is visible at a glance. Each thread should state: name, status, next action or blocker, and the canonical source file.

This file is a summary layer, not the canonical proof layer.

Write to LITERATURE_NOTES.md when

• a prior work, paper, article, or external source is read or referenced
• a source supports or challenges a hypothesis in HYPOTHESIS_LAB.md
• a methodological choice is informed by existing literature
• the relationship between external findings and this project's work should be recorded

Each entry should connect the source to this project's hypotheses, methods, or decisions. Do not just list references — explain relevance.

This file is used in the academic profile. If the profile is research or lower and this file does not exist, do not create it unless the user is working toward a publication.

Write to FIGURES_LOG.md when

• a figure, chart, diagram, or table is produced
• the user provides a photo, screenshot, figure, diagram, generated image, or other visual asset that may matter later
• a photo, screenshot, generated image, or external visual asset becomes part of the project
• a visualization is updated or superseded
• the data source, generation method, or intended use of a visual output should be traceable

When a visual file exists, is generated, or is provided by the user, save a durable copy under the project's figure asset directory before relying on it. The default directory is figures/ unless CONTEXT_MANIFEST.md declares another path.

Use stable figure IDs for filenames, such as figures/FIG-001.png, figures/FIG-001-source.png, or figures/FIG-001-final.svg. If the asset is not yet a formal figure, save it under figures/inbox/, for example figures/inbox/IMG-YYYY-MM-DD-001.png, and promote or link it to a FIG-xxx path later.

Each entry should link the visual asset path to its original source, data source, and generation method so it can be found, reproduced, or revised during peer review. Preserve the

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: tasuku-9
• Source: tasuku-9/project-memory-skill
• License: MIT

Install and usage instructions live in the source repository linked above.