Engrm Memory

Use this skill when continuity matters and Codex should not start from a blank session.

What this skill is for

• Pull relevant prior knowledge into the current session.
• Reuse past decisions, fixes, and discoveries before repeating work.
• Save new knowledge when the session produces something future work should know.
• Make cross-device and cross-agent memory genuinely useful.

When to use Engrm first

Use Engrm before coding when:

• work is resuming after a break
• the area looks familiar
• the task touches a bug, auth flow, deployment path, or refactor area that may

already have history

• the session starts on a different machine or with a different coding agent

Use Engrm during coding when:

• implementation starts drifting
• an earlier decision needs checking
• you suspect the same issue has been solved before

Use Engrm after coding when:

• a durable decision was made
• a bugfix or pattern is likely to recur
• the session discovered a lesson that future work should start with

Default workflow

1. Search or inspect recent activity first.
2. Pull timeline or session context if the area has recent churn.
3. Apply prior decisions before making changes.
4. Save only high-signal outcomes.

Good Engrm questions

• What do we already know about this area?
• Was there an earlier decision for this approach?
• Did a previous session touch the same files or subsystem?
• Is there a recent bugfix or security note I should reuse?

Save high-signal memories

Prefer saving:

• durable decisions
• bugfixes with clear cause and resolution
• discoveries that unblock later sessions
• patterns worth reusing

Avoid saving:

• obvious implementation details
• noisy dead ends
• generic filler that pollutes retrieval