Project memory organisation with an agent
Separate current state from history and approve changes before restructuring
Project memory organisation with an agent begins by choosing whether to view, update or migrate existing material. The project-handoff-memory skill separates these modes so discovering a file does not itself authorise rewriting or moving it.
Current state, durable decisions and progress history have different roles. Existing project rules can remain in place while you update the relevant material. An optional local checker reports structural and reference issues, but cannot prove that every statement is true or that a decision is still current.
What it does
- Separate current state from progress history
- Preserve existing project entry rules
- Identify uncertain or unconfirmed information
- Check local Markdown references
- Plan a migration before moving documents
- Limit changes to authorised files and roots
Install and use
- Load the skill in a file-capable agent with an explicit authorised project path. The optional read-only checker needs Python 3.
- For example: “Inspect this project’s memory and broken references without changing any files.”
- For edits, approve update mode and the affected files. For restructuring, review the migration map and preserved entry points first.
- Inspect the resulting documents and references. Treat file-age warnings as prompts to check content, not proof that it is obsolete.
FAQ
Source
Made by 阿亮 (liangyls). Original skill: project-handoff-memory, published on GitHub under the MIT licence.
View on GitHub