jotbook-stagelisted

# Stage a jot You just gave (or were asked about) an explainer the user wants to revisit later. Write a **lightweight** pointer file (a "jot") so the topic can be picked up during a future review pass. Do not write the full entry — that's `jotbook-ink`'s job. ## When to auto-invoke Auto-invoke this skill at the end of any turn that delivered a substantive multi-paragraph explanation of a domain concept — a system, mechanism, piece of code, or design rationale that the user might plausibly want to revisit as a long-form note later. Don't ask first. Just stage and report. Do NOT auto-invoke for: - Short answers, status updates, error messages - Code edits with minimal narration - Routine tool use or clarifications - Output from any jotbook skill (curation summaries, "the jot backlog is empty", `(jotted: X)`, etc.) - Trivial Q&A ("what's the syntax for X") - Anything you wouldn't expect future-you to benefit from a long-form entry on When in doubt, skip — the user can always invoke `/jot [subject]` explicitly. ## Resolve the jots directory Read `.claude/jotbook.local.md` if present. From its frontmatter, extract: - `jots_dir` — default `docs/jotbook/_jots/` if missing If the jots directory does not exist, create it. **Before running `mkdir`, briefly note to the user what you're doing and why** — something like *"Creating `<jots_dir>` to hold staged jots (first time staging in this project, or the directory was renamed in settings)."* This avoids a context-free permissio