notelisted

# Note Capture Distill session context into a succinct, frontmatter-rich markdown note. One note per invocation. Notes persist under `.rp1/work/notes/` w/ auto-maintained index and append-only log. ## Directories Use the pre-resolved `workRoot` from the generated Resolve Arguments section. All note paths resolve against `workRoot` -- never relative to a worktree. Set `NOTES_DIR` = `{workRoot}/notes`. ## Load Template Read the note template for format reference: ``` plugins/base/skills/artifact-templates/templates/note/note.md ``` Use this template as the canonical structure for the note file. Do not deviate from the frontmatter schema or section order. ## Generate Note ### Semantic Title Derive a descriptive title from session context (or TOPIC if provided). The title MUST communicate the note's subject at a glance. - Good: "API Rate Limiting Decision", "Memory Leak Root Cause in Worker Pool" - Bad: "Session Notes 2026-06-10", "Various Decisions" ### Slug Slugify title: lowercase, hyphens for spaces, strip non-alphanumeric chars. File path: `{NOTES_DIR}/{yyyy-mm-dd}-{title-slug}.md` ### Frontmatter Populate all required fields per template: | Field | Source | |-------|--------| | `date` | Today (YYYY-MM-DD) | | `title` | Generated semantic title | | `tags` | Inferred from session context; 2-5 tags | | `related` | Wikilink cross-references to relevant notes/artifacts (see below) | | `source_context` | One-line summary of session context | | `status` | `active