Capture meeting and coding session notes into indexed per-event markdown files with structured retrieval.
88
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Capture and retrieve structured notes from meetings and coding sessions.
~/.claude/notes/~/.claude/notes/index.md~/.claude/notes/<YYYY-MM-DD>-<slug>.mdZERO QUESTIONS RULE: When the user provides ANY text as arguments, NEVER ask clarifying questions. No asking about type, context, action items, or anything else. Infer everything from the text. Default type to session if unclear. Just capture and write immediately.
Batching rule: If multiple notes arrive in a session, accumulate them in memory and only write files when the user says "done" or explicitly asks to save. This keeps writes to one per session.
CRITICAL: DO NOT write to any note files until the user explicitly says "done" or "save". Until then, hold all captured content in conversation memory only. Acknowledge each input with a short confirmation but perform ZERO file writes. When "done" is said, write all accumulated notes in one batch.
session). Do NOT ask ANY questions — not about type, not about context, not about anything.-2, -3, etc.~/.claude/notes/<date>-<slug>.md:---
date: YYYY-MM-DD
type: meeting | session
title: Human-readable title
tags: [tag1, tag2]
---
# Title
## Key points
- ...
## Decisions
- ...
## Action items
- [ ] ...index.md if missing (with header row), then append:| Date | Type | Title | Tags | File |
|------|------|-------|------|------|
| 2026-04-29 | meeting | Sprint planning | #team | [2026-04-29-sprint-planning.md](2026-04-29-sprint-planning.md) |#tags, type filter, free text~/.claude/notes/index.md~/.claude/notes/ doesn't exist, create itindex.md is malformed, warn user and rebuild from note file frontmatter# in the table