notelisted

# Record an exploration note (work-docs) For work that has **no JIRA issue**: PoC, 검토(review), 코드 분석, and the like. Issue-keyed work goes through the **worklog** skill instead. Both write to the same public `work-docs` repo, side by side (issue records in uppercase-key folders, notes in lowercase category folders). ## Step 0: Prereqs - The public docs repo cloned at `${WORK_DOCS_REPO:-$HOME/Devel/work-docs}` (shared with worklog; the legacy `WORKLOG_DOCS_REPO` also works), with its `origin` set to your public repo. ## Step 1: Category and slug The invocation is `<category> <slug>`. **A category the user names wins over inference:** 1. **If the user named a category, use it verbatim** (lowercased). A leading ASCII word (`/note bug …` → `bug`), or any word matching an existing folder, is the category, even when the rest of the request describes the content: `/note bug 분석한 내용...` still means category `bug`, not `analysis`. 2. **Reuse an existing category** rather than inventing a near-duplicate (`bug` vs `analysis`). List them first (uppercase folders are worklog issue keys: skip them): ```bash REPO="${WORK_DOCS_REPO:-$HOME/Devel/work-docs}"; ls -d "$REPO"/*/ 2>/dev/null | xargs -n1 basename | grep -vE '^[A-Z]' ``` 3. **Only if the user named no category, infer one** that fits (`poc`, `review`, `analysis`, …). Then pick a short **slug**. **Before scaffolding, state the resolved `<category>/<slug>`**; if you inferred the category (step 3) or it would create a bran