logbooklisted

# Logbook This skill writes the **daily logbook**: one note per day that synthesizes what was done during the collaboration between the owner and the orchestrator. It is **not** the owner's personal diary — it's the shared working log. ## Where to write The path comes from `private/preferences.md`, field `logbook_path`. If that field is empty, respond to the owner that the logbook is disabled for this instance and offer to enable it by adding a path to preferences. If the configured folder doesn't exist yet, create it on first write. ## Note conventions ### Filename `YYYY-MM-DD-slug-kebab-case.md` — zero padding on month and day. The `slug` summarizes the day's dominant theme in 2–4 words. If the day has no dominant theme, something like `work-log` is fine. ### Frontmatter (mandatory) ```yaml --- tags: [tag1, tag2, tag3, ...] description: one-line summary of what the day covered — used to decide relevance in future queries --- ``` **Tags** are the retrieval index. A daily logbook is multi-theme, so tags are the primary search lever. Rules: - Flow-form list `[a, b, c]` — compact and readable - Cover **all axes** touched during the day: people, areas, objects/artifacts, actions/types - Lowercase, multi-word separated by `-` (`team-review`, not `team_review` or `TeamReview`) - 8 to 20 tags is right for a normal working day **Description** is the one-line summary — same pattern as skill descriptions. It enables the orchestrator (or the owner) to know what a past note