trail-scriberlisted

# Trail Scriber - Day-by-Day Conversation Trail Reconstruction ## When to use Use this when the user asks for any version of: - "go through my Codex and Claude conversations and tell me what I did" - "update my what-I-did-today list" - "do May 14 / May 13 / this week day by day" - "immortalise agendas", "make a trail", or "make the Obsidian graph intuitive" - "read the user messages and get the vibe" - "figure out what agenda this belonged to even if the folder was wrong" This skill is for reconstruction from evidence, not generic summarization. ## What you are doing You are turning scattered agent conversations into a durable work trail: - days show what happened on a calendar date - agendas show the actual workstreams - domains show bigger life/project areas - conversation/source notes preserve where the evidence came from - month notes explain silent spans instead of inventing activity The work is interpretive. Tools can locate candidate conversations, dates, roots, and session ids, but they must not replace judgment. ## Core posture Read like a colleague reconstructing a workday from traces, not like a keyword classifier. Prefer the user's messages. Assistant answers are optional evidence: read them only when the user's message is ambiguous, when a tool result is needed to confirm what happened, or when provenance matters. Do not lazily assign domains by hard-coded keyword rules. Keywords may help triage candidates, but the final agenda/domain call must come f