Id Document

The infra-delivery documentation step (step 16) — generate/update the change documentation (the change-record / ADR, the blast-radius summary, the runbook, the rollback note, and the changelog entry) a delivered IaC change requires, DERIVED from the RECORDED pre-merge plan step-report note + the plan summary and MATCHED to the surrounding repo''s existing doc conventions. A read-only doc-output PROCEDURE skill the generic agent runs: it READS the recorded `.foundry/`-partitioned `id-plan` step-report note (`actions_detail`) as the source of what changed, reads the blast tier from the same recorded observation, and sources the rollback note from the realization-frame `id-rollback` incident path (git revert → reconcile → verify-landed) — NOT from the `infra_binding.apply` forward-mutation slot. It records its OWN output as a `.foundry/` doc step-report NOTE (`.foundry/id-document-report`), NOT walk-evidence and NOT a verdict input (the bespoke `emit_infra_walk_evidence` recorder this note is contrasted against was retired and does not exist in scripts/). ADVISORY craft — it surfaces the documentation to the operator; it issues no mutating verb, decides no merge verdict, and flips no workflow step.

mkdir -p ~/.claude/skills/id-document
curl -L https://claudskills.com/skills/id-document/SKILL.md \
  -o ~/.claude/skills/id-document/SKILL.md

@misc{id-document-2026,
  author    = {lukasrepublic},
  title     = {Id Document [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/id-document/}
}