id-planlisted

The infra-delivery PRE-MERGE seam PROCEDURE skill (/foundry:id-plan, infra-delivery step 8). A read-only PROCEDURE — it resolves the active stack profile, drives the profile's infra_binding.plan command strings READ-ONLY (tofu plan + kubectl --dry-run=server + argocd app diff) against the real environment, collects the structured plan/diff (candidate vs merge-base, attributable), and produces the review artifact + a `.foundry/`-partitioned plan STEP-REPORT NOTE. It NAMES infra_binding.plan as its command source and the review artifact as its output. It issues NO mutating verb and does NOT self-certify a PASS. Honest disclosure: the bespoke `emit_infra_walk_evidence` recorder / `derive_walk_verdict` verdict machinery this skill used to name as its evidence backend and verdict authority were retired and do not exist in scripts/ — the merge floor (the adopter's branch protection + CI checks, see docs/merge-floor.md) is the merge authority now. ADVISORY craft FOR the trusted operator; it does NOT gate, approve, o
lukasrepublic/agentic-foundry · ★ 1 · Code & Development · score 67

Install: claude install-skill lukasrepublic/agentic-foundry

# /foundry:id-plan — the read-only PRE-MERGE seam (plan/diff → review artifact + step-report note) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an IaC change spec → merge. Step 8 is the **PRE-MERGE seam**: before an infrastructure change is merged, prove read-only that the change does what its spec says and nothing else — that the codified IaC, refreshed against the **real** environment, matches reality with no unexpected `add`/`change`/`destroy`/`replace` and a clean policy pass. Infrastructure has no app to boot, so the app live-seam (boot → exercise a surface → assert no new 5xx) has no analog here. `id-plan` is the disciplined procedure the generic agent runs instead: it resolves the active profile, drives the profile's **`infra_binding.plan`** command strings **read-only** against the real environment, collects the structured plan/diff, and turns it into **the review artifact** (the hand-off the human / `id-review` / the merge floor reads) plus a `.foundry/`-partitioned **plan STEP-REPORT NOTE**. The infra live-seam's dedicated walk-evidence recorder + verdict machinery this skill used to compose with was retired (see `docs/DESIGN.md`) — there is no live consumer that adjudicates this note into a PASS/FAIL today; it is advisory input for the human review at the merge floor. ## When to trigger - The `infra-delivery` sequence advances to the **pre-merge seam** (step 8), after