From claudecode-research-harness-workflow
Manages SSOT, project memory, and cross-tool memory search. Handles decisions.md, patterns.md, SSOT promotion, migration, merging, and sync. Use to save learnings or search past decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudecode-research-harness-workflow:memory [ssot|sync|migrate|search|record][ssot|sync|migrate|search|record]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A set of skills responsible for memory and SSOT management.
A set of skills responsible for memory and SSOT management.
| Feature | Details |
|---|---|
| SSOT Initialization | See references/ssot-initialization.md |
| Plans.md Merge | See references/plans-merging.md |
| Migration | See references/workflow-migration.md |
| Project Spec Sync | See references/sync-project-specs.md |
| Memory → SSOT Promotion | See references/sync-ssot-from-memory.md |
For recording and searching shared across Claude Code / Codex / OpenCode, prefer harness_mem_* MCP.
harness_mem_search, harness_mem_timeline, harness_mem_get_observationsharness_mem_resume_packharness_mem_record_checkpoint, harness_mem_finalize_session, harness_mem_record_eventHarness SSOT memory (Layer 2) coexists with Claude Code auto-memory (Layer 1).
Auto-memory implicitly records general learnings, while SSOT explicitly manages project-specific decisions.
When Layer 1 insights are important for the whole project, promote them to Layer 2 with /memory ssot.
Details: D22: 3-Layer Memory Architecture
Persist important learnings from memory systems (Claude-mem / Serena) into SSOT.
npx claudepluginhub maxwell2732/claudecode-research-harness-workflow --plugin claudecode-research-harness-workflowManages SSOT (Single Source of Truth), decisions.md, patterns.md, and cross-tool memory search. Handles memory migration, SSOT promotion, and sync operations via harness MCP tools.
PROACTIVELY query Forgetful MCP (mcp__forgetful__* tools) when starting work on any project, when user references past decisions or patterns, when implementing features that may have been solved before, or when needing context about preferences. Save important decisions, patterns, and architectural insights to memory.
Integrates sage-memory for persistent knowledge across sessions via MCP tools or file fallback. Automates recall at session/task starts and storage during work.