Maintain project memory

Skill ImYourBoyRoy/agent-continuity-stack/skills/maintain-project-memory

Repository-centered instructions, skills, memory conventions, client adapters, and lifecycle safeguards for consistent work across AI coding agents.

Install

npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill maintain-project-memory

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create, audit, compact, or synchronize the required MEMORY.md and related continuity artifacts. Use after meaningful project work, before a resumable handoff, or when project memory is missing, stale, unsafe, or duplicative.

SKILL.md

2.9 KB, 545 tokens by cl100k_base, as published. Nobody here has run it

Maintain Project Memory

Maintain a concise, current MEMORY.md for every maintained project. Use it to route future work without treating it as stronger evidence than source, Git, manifests, tests, builds, or verified runtime behavior.

Establish the foundation

Resolve the repository root, read project instructions and relevant README sections, inspect Git status, and locate MEMORY.md. If it is absent, create it unless the current request is strictly read-only or the repository forbids the change; in those cases, report the missing required foundation.

Keep MEMORY.md as the continuity index. Delegate deep or specialized content:

issues or TASKS.md own large backlogs and acceptance criteria
ADRs or ARCHITECTURE.md own deep durable design decisions
runbooks own repeatable operations
README.md owns stable usage and onboarding facts
CHANGELOG.md owns release history
temporary handoffs own short-lived execution state

Link or summarize those authorities without copying them. Read references/artifact-selection.md when ownership is unclear.

Synchronize compactly

Include only applicable:

project snapshot and useful working-directory map
current goals, active work, and exact next action
architecture notes, decisions, and conventions
verified resources and dated software-version findings
important commands and workflows
known issues, risks, and blockers
recent material changes
validation performed and its environment

Label observations, inferences, and proposals. Timestamp volatile external facts. Replace stale status instead of appending an endless transcript.

After meaningful work, synchronize completed and remaining work, important path changes, discoveries, decisions, risks, validation, and the next recommended action. Do not update memory merely to restate a trivial conversation.

Safety and privacy

Never record credentials, tokens, private keys, secret values, personal data, or sensitive production content.
Avoid absolute personal paths, private hosts, device IDs, and environment dumps.
Do not claim a model's private memory or chat history is an authoritative project source.
Keep durable guidance in version-controlled, human-reviewable artifacts.
Let current source, Git state, tests, and runtime evidence override old notes.

Handoff check

Before finishing substantial work, make sure another contributor can identify:

what is complete
what is incomplete
what evidence exists
what must not be repeated or assumed
the safest next action

Report the memory file used, stale material removed or flagged, related authorities updated, sensitive details excluded, and the next action.