name	memory-note
description	ALWAYS invoke when the user wants to manually save a note, decision, or convention into project memory. Triggers "remember that", "note this", "save to memory", "pin this decision", "add to memory". Pins go to the persistent Pinned section; activity entries go to the rolling Activity Log.
argument-hint	<note body> [--log to append to Activity Log instead of Pinned]
allowed-tools	Bash, Read, AskUserQuestion
model	haiku

Memory Note

Overview

Appends a single dated entry to .mz/memory/MEMORY.md. By default the entry goes to the Pinned section (persistent, never auto-pruned). Pass --log to append to the Activity Log instead (FIFO, capped at 200 lines).

When to Use

User says "remember that X", "note this", "pin the decision to use Y", "save to memory"
User reports a convention, invariant, or decision that should outlive the current session
User wants to leave a breadcrumb for the next session

When NOT to use

User wants to capture a completed task — that flows automatically through the SessionEnd hook
User wants to read or search memory — they should open .mz/memory/MEMORY.md directly
User wants to remove an entry — edit the file by hand

Input

$ARGUMENTS — the note body. Inline modifiers:

--log — append to Activity Log instead of Pinned (use for transient activity-style notes)

If $ARGUMENTS is empty, ask via AskUserQuestion. Never guess.

Constants

MEMORY_FILE: .mz/memory/MEMORY.md
NOTE_SCRIPT: ${CLAUDE_PLUGIN_ROOT}/scripts/memory-note.sh
MAX_BODY_CHARS: 500 (longer notes get rejected — split or summarize)

Core Process

Phase 0: Parse

Strip --log if present; remember it as target=log, otherwise target=pinned.
Trim whitespace from the remaining body.
If body is empty → AskUserQuestion for the note text. Never guess.
If body length > MAX_BODY_CHARS → ask user to shorten or split. Never silently truncate.

Phase 1: Confirmation Gate

This orchestrator (not a subagent) must present to the user via AskUserQuestion. This step is interactive and must not be delegated.

Mandatory pre-read: Compute the exact entry that will be written (- [YYYY-MM-DD] <body>) and capture it into context.

Before invoking AskUserQuestion, emit a text block to the user:

**Memory note ready to write**
About to add a single dated entry to the <target> section of .mz/memory/MEMORY.md.

- **Approve** → write the entry, surface the resulting line
- **Reject** → discard, no file changes
- **Feedback** → revise the body, re-present this gate

Invoke AskUserQuestion with this body:

Memory note preview:

  <verbatim entry line>

Target section: <pinned|log>

Type **Approve** to proceed, **Reject** to cancel, or type your feedback.

Response handling:

"approve" → run Bash NOTE_SCRIPT [--log] "<body>", then proceed to verification.
"reject" → stop. Do not write. Surface "Note discarded."
Feedback → revise the body using the user's input, return to this gate, re-present via AskUserQuestion with the new entry. This is a loop — repeat until the user explicitly approves.

Phase 2: Verification

After the script runs, output a visible final block:

Memory note written.
File:    .mz/memory/MEMORY.md
Section: <pinned|log>
Entry:   <verbatim entry line>

If the script exited non-zero, surface the stderr message and stop.

Common Rationalizations

Rationalization	Rebuttal
"skip the gate, just write it"	a wrong note pollutes pinned memory across every future session
"truncate the body silently"	the user will not notice the loss until the lost detail matters
"default to Activity Log"	log entries roll off; user-driven notes belong in Pinned

Red Flags

You wrote to MEMORY.md directly with Edit/Write instead of the helper script.
You skipped the approval gate.
You silently truncated a too-long body.
You guessed the note body when $ARGUMENTS was empty.

Error Handling

Empty body → AskUserQuestion for the text. Never guess.
Body > MAX_BODY_CHARS → ask user to shorten; do not truncate.
memory-note.sh exits 2 → surface stderr and stop.
memory-note.sh reports duplicate → surface the message; do not retry.

State Management

This skill is single-shot — no .mz/task/ state file is created. The only durable artifact is the line appended to MEMORY.md.

name	memory-note
description	ALWAYS invoke when the user wants to manually save a note, decision, or convention into project memory. Triggers "remember that", "note this", "save to memory", "pin this decision", "add to memory". Pins go to the persistent Pinned section; activity entries go to the rolling Activity Log.
argument-hint	<note body> [--log to append to Activity Log instead of Pinned]
allowed-tools	Bash, Read, AskUserQuestion
model	haiku

Memory Note

Overview

When to Use

User says "remember that X", "note this", "pin the decision to use Y", "save to memory"
User reports a convention, invariant, or decision that should outlive the current session
User wants to leave a breadcrumb for the next session

When NOT to use

User wants to capture a completed task — that flows automatically through the SessionEnd hook
User wants to read or search memory — they should open .mz/memory/MEMORY.md directly
User wants to remove an entry — edit the file by hand

Input

$ARGUMENTS — the note body. Inline modifiers:

--log — append to Activity Log instead of Pinned (use for transient activity-style notes)

If $ARGUMENTS is empty, ask via AskUserQuestion. Never guess.

Constants

MEMORY_FILE: .mz/memory/MEMORY.md
NOTE_SCRIPT: ${CLAUDE_PLUGIN_ROOT}/scripts/memory-note.sh
MAX_BODY_CHARS: 500 (longer notes get rejected — split or summarize)

Core Process

Phase 0: Parse

Strip --log if present; remember it as target=log, otherwise target=pinned.
Trim whitespace from the remaining body.
If body is empty → AskUserQuestion for the note text. Never guess.
If body length > MAX_BODY_CHARS → ask user to shorten or split. Never silently truncate.

Phase 1: Confirmation Gate

This orchestrator (not a subagent) must present to the user via AskUserQuestion. This step is interactive and must not be delegated.

Mandatory pre-read: Compute the exact entry that will be written (- [YYYY-MM-DD] <body>) and capture it into context.

Before invoking AskUserQuestion, emit a text block to the user:

**Memory note ready to write**
About to add a single dated entry to the <target> section of .mz/memory/MEMORY.md.

- **Approve** → write the entry, surface the resulting line
- **Reject** → discard, no file changes
- **Feedback** → revise the body, re-present this gate

Invoke AskUserQuestion with this body:

Memory note preview:

  <verbatim entry line>

Target section: <pinned|log>

Type **Approve** to proceed, **Reject** to cancel, or type your feedback.

Response handling:

"approve" → run Bash NOTE_SCRIPT [--log] "<body>", then proceed to verification.
"reject" → stop. Do not write. Surface "Note discarded."
Feedback → revise the body using the user's input, return to this gate, re-present via AskUserQuestion with the new entry. This is a loop — repeat until the user explicitly approves.

Phase 2: Verification

After the script runs, output a visible final block:

Memory note written.
File:    .mz/memory/MEMORY.md
Section: <pinned|log>
Entry:   <verbatim entry line>

If the script exited non-zero, surface the stderr message and stop.

Common Rationalizations

Rationalization	Rebuttal
"skip the gate, just write it"	a wrong note pollutes pinned memory across every future session
"truncate the body silently"	the user will not notice the loss until the lost detail matters
"default to Activity Log"	log entries roll off; user-driven notes belong in Pinned

Red Flags

You wrote to MEMORY.md directly with Edit/Write instead of the helper script.
You skipped the approval gate.
You silently truncated a too-long body.
You guessed the note body when $ARGUMENTS was empty.

Error Handling

Empty body → AskUserQuestion for the text. Never guess.
Body > MAX_BODY_CHARS → ask user to shorten; do not truncate.
memory-note.sh exits 2 → surface stderr and stop.
memory-note.sh reports duplicate → surface the message; do not retry.

State Management

This skill is single-shot — no .mz/task/ state file is created. The only durable artifact is the line appended to MEMORY.md.

memory-note

Memory Note

Overview

When to Use

When NOT to use

Input

Constants

Core Process

Phase 0: Parse

Phase 1: Confirmation Gate

Phase 2: Verification

Common Rationalizations

Red Flags

Error Handling

State Management

Memory Note

Overview

When to Use

When NOT to use

Input

Constants

Core Process

Phase 0: Parse

Phase 1: Confirmation Gate

Phase 2: Verification

Common Rationalizations

Red Flags

Error Handling

State Management