memory

To persist PM context across sessions, this skill reads and updates a memory profile to capture product context, stakeholders, roadmaps, risks, and lessons learned, ensuring accurate context without requiring a re-brief.

You need to update your PM memory profile at session boundaries, such as after finalizing PRDs, roadmaps, or stakeholder updates, ensuring new decisions and context are captured with timestamped, non-destructive writes.

Non-destructive memory persistence works by enforcing date stamps and schema-aligned rules when writing to the profile, preserving previous institutional knowledge while appending new product context and stakeholder updates.

Yes, you can use this skill to capture stakeholder context and lessons learned by applying memory updates whenever significant events occur, maintaining an accurate and up-to-date persistent profile for future reference.

The best way to maintain institutional knowledge for product roadmaps is to enforce memory schema guardrails and apply non-destructive, timestamped writes to a persistent profile after key product decisions are made.

No, PM memory persistence does not require external dependencies; it functions independently to read, write, and maintain the user profile file by enforcing internal schema rules and date stamps.