Rohi Rikman

Spec

Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria' before planning or implementing a feature or bug fix.

MemoryReview

Curation pass over OpenLTM memory: triage pending session-end proposals, stale-flagged memories, conflicting or superseded entries, and low-value duplicates, then accept, revalidate, relate, or forget them with the user's approval. Use when the user says 'review memories', 'clean up memory', 'curate LTM', 'what's pending', 'any memory proposals', 'prune stale memories', or after a refactor that may have invalidated what LTM knows.

Ltm

OpenLTM long-term memory: tool names, the recall-before / learn-after ritual, categories, project context, and what the hooks already inject. Use when the user says 'remember this', 'save this gotcha', 'what do we know about X', 'did we decide on Y before', 'forget that memory', 'link these memories', 'restore project context', 'set the project goal' — or before non-trivial work that may touch past decisions.

GitLearn

Mines durable LTM memories from past git commits through the git-learner agent (no API key needed). Use when the user says 'learn from our git history', 'mine the last N commits', 'backfill memories since <date>', 'onboard this repo into LTM', or wants to harvest patterns after a sprint.

secret-safe-handling

USE WHEN handling credentials, env vars, logs, tests, or docs safely.

command-path-safety

USE WHEN hardening command execution, path handling, or installer boundaries.

agent-trust-boundaries

USE WHEN separating trusted instructions from untrusted content or tool output.