From harness
Use this skill whenever the user mentions SSOT, decisions.md, patterns.md, memory search, save learnings, record a decision, harness-mem, sync memory, promote patterns, merge plans, migrate memory, or recall past decisions. Also use when the user wants to persist cross-session knowledge or search for previously recorded patterns. Do NOT load for: code implementation, code reviews, ad-hoc notes, or in-session task logging. Manages SSOT (Single Source of Truth) memory — decisions.md, patterns.md, cross-tool memory search, and memory sync.
npx claudepluginhub tim-hub/powerball-harness --plugin harnessThis skill is limited to using the following tools:
A collection of skills responsible for memory and SSOT management.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A collection of skills responsible for memory and SSOT management.
| Feature | Details |
|---|---|
| SSOT Initialization | See references/ssot-initialization.md |
| Plans.md Merging | See references/plans-merging.md |
| Migration Processing | 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 the harness_mem_* MCP tools.
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's 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 entire project, promote them to Layer 2 with /memory ssot.
Details: D22: 3-Layer Memory Architecture
Persists important learnings from the memory system (Claude-mem / Serena) to SSOT.