Id Implement

The infra-delivery change-authoring craft (step 5) — author/edit the IaC for the intended change ON A BRANCH, kept in sync with the frozen intended-change manifest (the `tofu-plan` checkpoint''s operator-frozen `intended` set in the acceptance-contract). A PROCEDURE skill the generic agent runs inside a CTX session: it WRITES files (scaffold/edit the OpenTofu/Kubernetes IaC to the handbook conventions) and runs NO plan and mutates NOTHING. The load-bearing discipline: the authored IaC is BRANCH-QUARANTINED (never `main`) and NEVER-APPLY (no `tofu apply`/`kubectl apply`/live mutation here), and it stays in sync with the frozen `intended` set so the downstream read-only `id-plan` plan can attribute it for the operator/reviewer. Records a `.foundry/id-implement-report` authoring STEP-REPORT NOTE — NOT walk-evidence, NOT a verdict input (the bespoke `emit_infra_walk_evidence` plan recorder this note is contrasted against was retired and does not exist in scripts/). ADVISORY craft, NOT a gate — the merge floor (branch protection + CI checks, see docs/merge-floor.md) is the authority.

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

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