daybrieflisted

# daybrief — morning work briefing `/daybrief [plain-language steering, e.g. "skip email", "just repos", "save it"]` Answer one question in one scan: **what needs my attention today, in what order?** Pull every source in parallel, compress hard, and lead with the priorities — not the raw data. Target: the user reads it in under two minutes. ## Step 0 — Config Look for `daybrief-config.md` in the current working directory. It defines: ```markdown # daybrief config ## Repos # absolute paths, or workspace roots to scan one level deep - /home/hop/code ## Tasks # optional: where your todos live (any/all of these) - file: TODO.md # a local markdown todo file (path relative to a repo or absolute) - github: assigned # issues assigned to you, via `gh` if authenticated ## Radar topics # 2–4 topics to check for movement - claude code - postgres ## Preferences - timezone: Asia/Ho_Chi_Minh - email: on # on / off - calendar: on # on / off - save: off # on = also write brief to out/daybrief/ (enables carry-over) ``` If missing, **don't block**: run with what's inferable (current repo, no radar topics). Then, **after** delivering the brief, offer to create the config via a short interview — ask (in one compact question set, prefilled with what you learned this run): which repos/workspace roots to watch, 2–4 radar topics, where todos live (file path / GitHub / none), email & calendar on/off, and whether to save briefs (`save: on` enables