Refresh Generated Context

Use when the knowledge base changed during a delivery run and its generated artifacts must be rebuilt: rebuilding the graph index and validating generated indexes against the changed content. This is the refresh_generated_context action of the knowledge-maintenance stretch — one Agent-tool dispatch with subagent_type devops-ops — the tooling-execution step, distinct from the documentation-steward actions around it that decide what changed and record the evidence.

BhangeeF16 Updated 0 repo stars

File contents

Refresh Generated Context

Rebuild the generated layer so the graph index reflects what the run just changed. Generated artifacts are never hand-edited — they are regenerated or their failure is recorded.

Dispatch

One synchronous Agent-tool call, subagent_type: devops-ops.

Required inputs

  • The changed knowledge base — which docs and manifests this run touched.

Required outputs (all mandatory)

  • Generated index validation — the regenerated artifacts checked against the changed content.
  • Graph reindex output — the actual tooling output, with a grep smoke proving the changed content is discoverable.

Rules — harvested documentation discipline

  • When the refresh genuinely cannot run (tooling unavailable, not merely "not run yet"), stop and record exactly why — the explicit record is this action's valid output in that case; silence is not.

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 commit e7eefdd2fc

Frequently asked questions

npx get-skill add bhangeef16/refresh-generated-context