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 Pick a free-form **lowercase category** (e.g. `poc`, `review`, `analysis`, or anything that fits) and a short **slug**. **Write the note in Korean.** The date is added automatically (`YYYY-MM-DD`). ## Step 2: Scaffold the file ```bash bash <skill-base-dir>/assets/new_note.sh <category> <slug> ``` Creates `<category>/<YYYY-MM-DD>-<slug>.md` from the template (refuses to overwrite) and prints the local path plus the public GitHub URL. Category and slug are lowercased and sanitized. ## Step 3: Investigate (use the lookup / analysis skills) Before writing conclusions, actively ground the note with the collection's investigation skills. Do not assert a fact from memory when a lookup can verify it: - **cubrid-manual**: CUBRID engine SQL syntax, functions, data types, reserved words, and config parameters (for engine-behavior review or code analysis). - **cmt-manual**: CUBRID Migration Toolkit behavior, source-type mapping, and opti