← ClaudeAtlas

ki-work-housekeepinglisted

Governs recurring repository housekeeping templates: their placement, identity, cadence, last-run evidence, and safe due-run spawning through ki-next. Use for "add recurring maintenance", "define housekeeping", "audit housekeeping", or "create a monthly repository check". In a non-KB repository templates live in docs/housekeeping; in a Knowledge Base they live in Streams/Housekeeping. It does not perform runtime-specific state cleanup, which is ki-housekeeping-claude.
knowledgeislands/ki-agentic-harness · ★ 0 · AI & Automation · score 76
Install: claude install-skill knowledgeislands/ki-agentic-harness
# Knowledge Islands housekeeping standard **Kind:** governance. `ki-work-housekeeping` owns recurring-work templates, not the delivery of a particular run. The shared forward-work lifecycle is owned by `ki-work-roadmap`; `ki-repo-kb-streams` places KB records under `Streams/Roadmap/`. Read [the housekeeping template standard](references/standards-housekeeping.md) before creating or changing a template, [the generated rubric](references/rubric.md) for checkable criteria, and [the sources](references/sources.md) when refreshing this standard. ## Shared model A housekeeping template is a durable instruction to create ordinary work when its cadence becomes due. It has a small lifecycle: `active` templates are evaluated, `paused` templates are retained but never spawn work, and a retired template is deleted. Due and overdue are calculated from `cadence`, `last-run`, and `grace`; they are not stored states. In a non-KB repository templates live directly below `docs/housekeeping/`. In a KB, the equivalent template notes live at `Streams/Housekeeping/`; it is an operational area, not a delivery state. `ki-next` reads active templates and atomically creates a linked `draft` run at the template's declared horizon while setting `active-run`. The run then follows the common `draft` → `ready` → `in-progress` → `awaiting-review` → `done` lifecycle. `ki-accept` records successful run evidence on the template only after the run is `done`. It never marks a template as run merely because