القائمة
Restore working context from Ferrosa Memory at the start of a session (or after /clear) before doing anything else. Use at session start, after compaction, or when resuming work on a repo.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Force a Ferrosa Memory consolidation pass at the end of a productive session so the dream cycle (edges, scenes, profiles) runs now instead of on the idle timer. Use at wrap-up, when the user says "that's it for now", or before a long break.
Capture deferred/follow-up work to the forge task board so it isn't lost. Use when you surface work you won't do now — out-of-scope items, prerequisites, follow-ups, "leave for later", known gaps. Pairs with /whats-next and /roadmap.
Build a roadmap for a repo by combining deferred work from the forge task board with a live TODO/FIXME scan of the repo, synthesized into themed, prioritized Now/Next/Later. Use when asked for a repo's roadmap, backlog, or debt plan.
Declare a time-bounded fact or temporary constraint in Ferrosa Memory (valid_from / valid_until). Use when something only holds for a window — a deadline, code freeze, deprecation, or planned-future change — so search surfaces it only while it is valid.
Answer "what's next?" by surfacing open deferred/follow-up work for the current repo from the forge task board, ranked. Use when asked what to work on next, what's outstanding, or to resume work.
| name | memory-session-start |
| description | Restore working context from Ferrosa Memory at the start of a session (or after /clear) before doing anything else. Use at session start, after compaction, or when resuming work on a repo. |
Ferrosa Memory is a semantic memory the agent should consult first, not as a
fallback. At the start of every session (including after /clear or compaction),
restore context before reading files or asking the user to re-explain.
Do this automatically — don't wait to be asked.
Gather cheap signals. Current git branch (git rev-parse --abbrev-ref HEAD)
and the last few commit subjects (git log --oneline -5).
Check prospective memory. Call check_intentions with a short description of
what you're about to do (branch + recent commits as context). Act on anything it
returns — these are "remember to do X when Y" notes left in earlier sessions.
Search for active work. Call hybrid_search with the branch name plus
keywords from the recent commits. Read what comes back instead of grepping. For
document_chunk hits, call get_context_window to pull adjacent chunks.
Summarize out loud. Tell the user, in 2–3 lines, what you remember about the
current work so they know you have context (e.g. "Last session you were wiring the
foresight retrieval filter; PR #121 is open; the set_foresight tool is now
tier-1."). If memory returns nothing useful, say so plainly.
Agents lose all working context across sessions and compaction. The memory server persists entities, relationships, scenes, profiles, and intentions across sessions — restoring from it turns "explain everything again" into a 2-second recall.
check_intentions + hybrid_search) cost ~15 ms total. Always worth it.hybrid_search also surfaces a session
profile (the workspace gist) and scenes (coherent entity clusters) — these are
built automatically by background consolidation.consolidate-wrapup (run at the end of a
session) and set-foresight (declare time-bounded facts).