jotbook-reviewlisted

# Review the jot backlog The user is reviewing the jot list to decide which subjects still feel worth inking into a long-form entry — or worth penciling first as a provisional draft before committing. Your job is to **surface and recommend**, not to delete or merge unilaterally. Every destructive action needs explicit confirmation. ## Resolve configuration Read `.claude/jotbook.local.md` if present. From its frontmatter, extract: | field | default | meaning | |---|---|---| | `jots_dir` | `docs/jotbook/_jots/` | where staged jots live | | `pencils_dir` | `docs/jotbook/_pencils/` | where pencils live — checked to flag jots that already have one | If `jots_dir` doesn't exist or contains no jots, report that in one line and stop. ## Procedure ### 1. Inventory List every `*.md` file under `jots_dir` (excluding any `README.md`). For each, read the file and extract: - Slug (filename without `YYYY-MM-DD-` prefix and `.md` suffix) - `staged:` date - Age in days (today − staged date) - Description line - Files line (if present) - **Pencil status**: check whether `<pencils_dir>/<slug>.md` or `<pencils_dir>/<slug>.html` exists. If so, note "has pencil from `<drafted-date>`" (and "revised `<date>`" if the pencil's frontmatter has a `revised:` field). Sort by age, oldest first. ### 2. Detect overlap Group jots that look topically related. Signals: - Overlapping file references on the `Files:` line - Shared keywords or domain terms in descriptions - Same subsystem or topic clus