メニュー
Use when maintaining session notes that must preserve a fixed markdown template, stay within section and total token budgets, and remain useful after compaction or resume
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when verifying implementation work and the failure mode is superficial approval, code-reading in place of execution, or over-trusting a passing test suite without trying to break the change
Use when coordinating multi-step work across workers or subagents, especially when research, implementation, and verification should be split while the main agent stays responsible for synthesis and user communication
Use when the task is codebase exploration rather than modification, and you need a fast, read-only search pattern that starts broad when location is unknown, narrows when location is known, and parallelizes independent searches
Use when deciding what information belongs in memory, how to classify it, and what must not be saved because it is derivable from the repo, git history, or current task context
Use when deciding whether shell commands are truly read-only, safe for concurrent execution, and free of path, git, redirection, or command-shape risks that should force a stricter permission path
Use when the real risk is not lack of knowledge but self-justifying shortcuts such as explaining instead of running commands, skipping the hard part first, or deciding on your own that verification would take too long
| name | session-memory-maintenance |
| description | Use when maintaining session notes that must preserve a fixed markdown template, stay within section and total token budgets, and remain useful after compaction or resume |
This skill is for structured session notes, not freeform journaling. It follows the template and update rules in src/services/SessionMemory/prompts.ts and the extraction lifecycle in src/services/SessionMemory/sessionMemory.ts.
The default session memory is organized around:
Keep each update in the right section. Do not duplicate the same fact across many sections.
Prioritize:
Skip filler. Blank is better than noise.
This codebase enforces both per-section and total-budget pressure.
When notes get too large:
Do not let session memory turn into a transcript copy.
Good session memory contains:
Avoid:
You have applied this skill correctly when the notes stay structurally intact, info-dense, compact enough to load, and immediately useful for resuming the session later.
