agentleFS
jukrapjukrap/ai-agent-playbook/skills/project/project-memory/SKILL.md

project-memory

Skill2 starsChanged 4 months agoMITView on GitHub

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

24 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the project's existing record entrypoint, such as CURRENT.md, for the active objective, constraints, next action, and links.

    line 8
  2. Very specific:

    Read references/current-state.md when updating current state or resuming work.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.