project-memory-cli
v0.1.1
Published
Plain-markdown project-memory layer for your repo. npm i -g project-memory-cli; CLI: project-memory.
Maintainers
Readme
project-memory
CLI: project-memory · npm: https://www.npmjs.com/package/project-memory-cli
The file system is the system. Structure defines execution. Agents are interchangeable executors.
project-memory is a filesystem convention plus a CLI that scaffolds a plain-markdown “project memory layer” inside your repo — so AI coding tools can read real project context instead of reconstructing it from scratch.
Spec: v1.0.0 — SPEC.md
Why this exists
AI tools are powerful, but they:
- lose context between tasks
- guess architecture from code
- duplicate work or break things
project-memory solves this by making context explicit and persistent.
- Predictable layout — One folder (
project-memory/), no hidden state - Tool-agnostic — Works with Cursor, Claude, Codex, or anything that reads a repo
- Git-native — Everything is plain Markdown, diffable, and reviewable
It is not:
- an agent framework
- a runtime
- a plugin system
Install
npm install -g project-memory-cliThen run:
project-memory initPackage name:
project-memory-cliCLI command:project-memory
Quickstart
mkdir my-project
cd my-project
project-memory init
project-memory tree
project-memory validate
project-memory new task "Build login page"Commands
project-memory init
Detects your repo, shows a scaffold plan, then writes the structure under project-memory/.
project-memory init
project-memory init --yes
project-memory init --new
project-memory init --existingproject-memory new task "<title>"
Creates a new task folder and updates the active task list.
project-memory new task "Build login page"Creates:
project-memory/tasks/TASK-NNN/project-memory new workflow "<title>"
Creates a workflow folder for multi-step work.
project-memory new workflow "User onboarding"project-memory tree
Prints a clean ASCII view of your project-memory structure.
project-memory treeproject-memory validate
Validates the base structure against the spec.
project-memory validateExample structure
After running init:
project-memory/
├── README.md
├── project/
│ ├── overview.md
│ └── architecture.md
├── context/
│ └── decisions.md
├── tasks/
│ └── active.md
├── tools/
│ └── global-tools.md
├── data/
└── workflows/Optional at repo root:
AI.mdThis file points AI tools to the correct entrypoints.
Using with AI tools
The workflow is simple and consistent:
- Open the repo
- Have the AI read the project-memory layer
- Execute tasks using structured context
Recommended read order
Cold start:
project-memory/project/overview.mdproject-memory/context/current-state.mdproject-memory/tasks/active.md
Assigned task:
project-memory/tasks/TASK-XXX/instructions.mdproject-memory/tasks/TASK-XXX/context.mdproject-memory/tasks/TASK-XXX/tools.md
Works with:
- Cursor
- Claude Code / Cowork
- Codex
- Any repo-aware AI
Philosophy
- The file system is the system
- Structure > prompts
- Context is stored, not inferred
- Everything is visible and editable
Contributing
See CONTRIBUTING.md
License
MIT — see LICENSE.md
