notes-mlisted

# Notes (notes-M) A generic persistent-note primitive. Each topic = a self-contained folder (`<topic-slug>-notes.md` + supporting artifacts). The folder is the source of truth; topics live across sessions. **Naming convention**: main file = `<topic-slug>-notes.md` where `<topic-slug>` is the folder name with the leading `YYYY-MM-DD-` stripped. Example: folder `2026-06-26-claude-setup/` → file `claude-setup-notes.md`. In legacy mode (d, single file no folder), file name = `<YYYY-MM-DD>-<topic-slug>.md`. ## When to use - User starts a multi-step investigation, debugging session, design discussion, data analysis, or brainstorm — anything that will span more than ~5 substantive turns - User explicitly invokes (`/notes-M`) or another skill (e.g. `grill-me-M`) delegates file mechanics here - User mentions: "take notes", "let's analyze", "let's dig into", "let's design", "investigate", "debug", "trace" Don't use for: simple one-shot Q&A, well-scoped code edits, tasks with their own deliverable. ## Step 1 — Resolve the location **Default structure** (when parent exists or user accepts the proposal): ``` <parent>/ ← default: notes/ └── <YYYY-MM-DD>-<topic-slug>/ ← topic folder ├── <topic-slug>-notes.md ← main file (folder name minus `YYYY-MM-DD-` prefix) └── <side artifacts> ← reports, exports, diagrams, etc. ``` ### 1.a — Derive the slug Short kebab-case from the topic (e.g. `auth-login-flow-investigation`, `mart-freshness-drift