torarnv Memory Skill
Ad-hoc project memory management. Use to record something mid-session without
running a full /end.
Trigger phrases: "remember this", "note that", "record a decision", /cpr:memory.
Memory file semantics
| Content type | File |
|---|---|
| Architectural or design decision | decisions.md |
| Workflow friction or process lesson | lessons.md |
| CLI syntax, missing tool, flag trap, argument quirk | tools.md |
| Update to project goal or scope | spec.md |
| New phase, task, or open question | plan.md |
| Current state update | status.md |
Workflow
Step 1: Identify the target file
Determine where the content belongs using the table above. If ambiguous, ask the user which file is appropriate.
Step 2: Check workspace scope (workspace mode only)
If .memory/tasks/ exists, this is a workspace. Determine whether the content is:
- Cross-task — relevant to future tasks in general → write to root-level file
- Task-specific — relevant only to the current task → write to the task file or task directory
If unclear, ask the user.
Step 3: Write the content
Append to the appropriate file. If the file doesn't exist, create it with frontmatter:
---
name: {{Name}}
description: {{one-liner for MEMORY.md index}}
type: {{decisions|lessons|tools|spec|plan|status}}
---
For lessons.md, include this note at the top if creating for the first time:
_For tool-specific knowledge (CLI syntax, missing tools, flag traps), see [tools.md](tools.md)._
Step 4: Sync index
If a new file was created, add it to .memory/MEMORY.md with a one-line entry:
- [Title](file.md) — one-liner description