Keep project memory canonical
Routes persistent work through specialist skills for memory maintenance, audits, file organization, repair, bounded recovery, and evidence-based completion.
Skills 8 in the ChatGPT listing
Auditing persistent state Use when inspecting a persistent project or Library to determine canonical locations, file roles, memory ownership, references, duplicates, stale state, evidence completeness, or the safe target state before mutation. Maintaining memory keeper Use when creating, editing, testing, auditing, packaging, versioning, releasing, or preparing publication of the Memory Keeper plugin or any of its skills. Maintaining project memory Use when a project gains, changes, validates, abandons, or depends on durable truth that future work must remember, including architecture, behavior, bugs, baselines, constraints, versions, tests, canonical locations, or memory structure. Organizing persistent files Use when moving, renaming, archiving, deleting, deduplicating, replacing, or reorganizing persistent project files, folders, release artifacts, or ChatGPT Library items. Recovering persistent work Use when a persistent read, write, move, rename, delete, upload, or verification times out, is interrupted, partially succeeds, returns ambiguous status, repeatedly mismatches, or resumes after a mid-transaction stop. Repairing memory state Use when persistent project memory is inconsistent, duplicated, stale, broken, orphaned, contradictory, ambiguously rooted, or has invalid routes after moves, renames, replacements, or partial repairs. Using memory keeper Use when a task involves ChatGPT Library, persistent project files, project memory, durable project code or docs, lasting decisions, structural cleanup, interrupted persistent work, or a completion claim about persistent work. Verifying persistent work Use when about to claim persistent project work is complete, done, fixed, organized, saved, synchronized, updated, cleaned, migrated, or successfully written. 