memory

The Memory skill acts as the centralized system for managing persistent project state, architectural decisions, and learned patterns within the Claude Code Harness environment. It serves as a bridge between transient session data and long-term project knowledge, ensuring that the AI agent maintains consistency across long-running development lifecycles. By acting as the guardian of critical documentation like decisions.md and patterns.md, it prevents configuration drift and ensures that historical technical choices are respected in future implementation phases. This skill is designed for senior developers and architects who require a disciplined approach to managing project documentation alongside automated coding tasks. It transforms Claude from a stateless script writer into a long-term development partner that understands the rationale behind codebase structures and past engineering trade-offs.

• Orchestrates the maintenance of the Single Source of Truth (SSOT) via automated synchronization and merging of Plans.md and related documentation.

• Integrates with harness-mem tools to perform cross-session memory searches, timeline reviews, and event retrieval across various AI models including Claude Code, Codex, and OpenCode.

• Facilitates the promotion of implicit learnings from Layer 1 (automatic memory) to Layer 2 (project-specific SSOT) using the /memory ssot command, ensuring valuable insights are permanently codified.

• Supports standardized workflow migrations and project specification synchronization, ensuring that team-wide standards are applied consistently during refactoring or new feature development.

• Use this skill specifically when the user explicitly requests memory management, SSOT promotion, or a review of past project decisions documented in md files.

• Do not trigger this skill for ad-hoc coding, reviews, in-session logging, or routine implementation work, as it is strictly reserved for high-level state management and organizational consistency.

• When engaging with Memory, ensure you leverage the harness_mem_* MCP tools for reliable data fetching, ensuring that queries are consistent with the 3-layer memory architecture (Layer 1: Auto, Layer 2: SSOT, Layer 3: Documentation).

• Always reference the specific guides in the references directory (such as ssot-initialization.md or workflow-migration.md) before executing state changes to avoid overwriting existing project specs.