Refresh Domain

Rebuild one domain's data/ layer from its inputs/ and connected sources. Run before `today` when data is stale.

Abaans Updated

File contents

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

  1. Parse inputs/ files into structured items (goals, projects, contacts — whatever the domain keeps there).
  2. Pull current state from connectors if configured (open issues, unread threads, upcoming events). Read only — connectors are sources, never storage.
  3. Cross-reference with objects/ frontmatter; note mismatches (e.g. an object says doing but the tracker says closed) as a conflicts array in the JSON — do not resolve them silently.
  4. Write data/summary.json with a generated_at timestamp.

Rules

  • NEVER write to inputs/ — this is the rule this skill is most tempted to break. Refresh output goes to data/ only.
  • Overwrites of data/ are safe by design; nothing hand-authored lives there.

Abaans/agent-spine/tree/main/toolbox/refresh-domain commit f965d2bc05

Frequently asked questions

npx skillmds@latest add abaans/refresh-domain