loglisted

# log — one day, one file Assembles a day's work log from the tracker the task skills already use, plus a calendar and chat where you name them, and writes it as a single markdown file. Reads everywhere, writes one place: a file under `log.out.dir`. Nothing is written back to the tracker. Built for a scheduler. It runs with nobody watching, so the rules below lean hard on *say what you could not do* rather than *fill it in anyway*. **It records; it does not appraise.** These files are the raw material a later review turns into accomplishment statements — that is `/pm:log-review`. This skill's job is to capture, on the day, the things that cannot be reconstructed months later: who said what about your work, what was decided and why, and the link that proves a piece of work existed. It never rates the importance of anything, and it never writes a sentence a source did not supply. ## Principles - **Never ask.** There is no one to answer. A missing value is skipped and named in the closing summary. - **Never invent.** Every line traces to something a source returned. An empty section gets `log.empty_line`, not a plausible sentence. - **Quote, do not characterise.** Praise, criticism and decisions are recorded in the words they were said in, with a link. Do not summarise someone's opinion into your own phrasing — a later review needs the original. - **Read the tracker's schema before querying it.** Property names drift and differ per workspace. Fetch the data source and use t