Research Project Memory

Maintain project memory as a layered system, not a flat notes file. This skill gives agents a shared protocol for remembering what a research project is trying to prove, what evidence exists, what risks remain, and which component owns each next action.

Use this skill when:

• a project needs cross-session memory beyond remote execution state
• the user wants memory across paper/, code/, worktrees, slides/, reviewer simulation, or rebuttal
• claims, experiments, figures, paper sections, reviewer risks, and actions need to stay aligned
• a session materially changes project direction, evidence, writing, review risks, or planned experiments
• a new agent session needs bootstrap context before acting
• the user asks for a memory system, project state graph, claim/evidence board, worktree memory, or closeout protocol

This is a coordination skill. It does not replace remote-project-control, experiment-design-planner, conference-writing-adapter, paper-reviewer-simulator, or rebuttal-strategist; it tells them where and how to persist trusted project state.

Skill Directory Layout