/save

Setup

1. Read ${CLAUDE_PLUGIN_ROOT}/config.json → extract vault.path.
2. Read notes.yaml from the current working directory → extract folder. If missing, tell the user to run /notes:init first and stop.
3. Resolve full notes directory: {vault.path}/{folder}/
4. Use Bash to expand any tilde in the path and mkdir -p the directory.

Determine target file

1. Check if you already wrote a note file earlier in this conversation. If so, reuse that path.
2. Otherwise, Glob for {notesDir}/${today's YYYY-MM-DD}-*.md.
3. If matches exist, read them and pick the one whose topic best matches this session's work.
4. If no match (or no existing files), generate a new filename: YYYY-MM-DD-{slug}.md where {slug} is 2-4 words in kebab-case describing the subject matter (not the activity — e.g. auth-token-rotation not debugging-auth).
5. If $ARGUMENTS is provided and non-empty, use it as the slug or as a hint for generating the slug.

Write the note

Reflect on the full conversation. Produce a note with this structure:

---
date: YYYY-MM-DD
tags:
  - session-notes
  - {folder}
---

# {Descriptive Title}

## Summary
1-3 sentences.

## What was accomplished
Bulleted list of concrete outcomes.

## Decisions
**{decision}** — {rationale}. If a decision was reversed mid-session, document only the final decision with a brief note on why the earlier approach was abandoned.

## Open questions
Unresolved items.

## Next steps
Concrete actions for the next session.

## Context for future sessions
Key state a fresh session needs: file paths, patterns, constraints, partial work.

Writing rules

• Omit empty sections — if nothing fits a section, leave it out entirely. Exception: always include Summary.
• Be concrete — file paths, function names, specific decisions. Not vague descriptions.
• Terse, scannable prose — this is a reference doc, not a narrative.
• If updating an existing file — read it first, reconcile stale info against what actually happened in this session, reflect current truth. Drop or revise anything superseded.
• Full file replace every time — use the Write tool to overwrite the entire file.

After writing

Report the file path to the user so they can find it in the vault.