refresh-domain
Usage: refresh-domain <domain> (e.g. refresh-domain work).
Reads
<domain>/inputs/— the human-maintained ground truth<domain>/objects/frontmatter- Connected sources for this domain (issue tracker, email, calendar) — read-only
Writes
<domain>/data/summary.json— overwrite entirely, every run
Steps
- Parse
inputs/files into structured items (goals, projects, contacts — whatever the domain keeps there). - Pull current state from connectors if configured (open issues, unread threads, upcoming events). Read only — connectors are sources, never storage.
- Cross-reference with
objects/frontmatter; note mismatches (e.g. an object saysdoingbut the tracker says closed) as aconflictsarray in the JSON — do not resolve them silently. - Write
data/summary.jsonwith agenerated_attimestamp.
Rules
- NEVER write to
inputs/— this is the rule this skill is most tempted to break. Refresh output goes todata/only. - Overwrites of
data/are safe by design; nothing hand-authored lives there.