Detect Drift

Use when a completing delivery run must check the knowledge base for drift its changes introduced or exposed: manifests, maps, and changed docs compared against reality, producing a drift report and a canonical-fact sync check. This is the detect_drift action of the knowledge-maintenance stretch — one Agent-tool dispatch with subagent_type documentation-steward — the finder, distinct from repair-manifest-and-links (the fixer that consumes its report).

BhangeeF16 d4fc0a8 1.5 KB Updated

File contents

Detect Drift

Find where recorded knowledge and reality disagree. This action reports drift; it deliberately fixes nothing, so the repair is itself reviewable.

Dispatch

One synchronous Agent-tool call, subagent_type: documentation-steward.

Required inputs

  • The manifests.
  • The maps/indexes.
  • The changed docs from this run.

Required outputs (all mandatory)

  • A drift report — every stale path, dangling link, out-of-date manifest entry, and duplicated or contradicted fact found.
  • A canonical-fact sync check — for each fact the run touched, confirmation its canonical owner says what reality now says.

Rules — harvested documentation discipline

  • A fact whose canonical owner cannot be determined is a stop condition — report it as a question, never resolve it by picking or inventing an owner.

Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).

BhangeeF16/kaizen/tree/main/skills/detect-drift commit d4fc0a86f1

Frequently asked questions

npx skillmds@latest add bhangeef16/detect-drift