i4h Workflow - Create Env

i4h Workflow - Create Env

Purpose

Create the first runnable version of a new workflows/agentic environment by forking the closest existing env. Keep this skill focused on env scaffolding: YAML, assets, task, env class, runtime, and validation. Do not use this skill to polish an existing scene, add optional props/cameras, or bake bridge edits; use [[i4h-workflow-scene-edit]] for that.

Base Code

Resolve and work from the i4h-workflows root:

ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"
if [ ! -d "$ROOT/workflows/agentic" ]; then
  ROOT="${I4H_WORKFLOWS:-$HOME/i4h-workflows}"
  [ -d "$ROOT/workflows/agentic" ] || git clone https://github.com/isaac-for-healthcare/i4h-workflows "$ROOT"
fi
export I4H_WORKFLOWS="$ROOT"; cd "$ROOT"

What to Load

Before editing, load only the references that match the request:

• Always load skills/i4h-workflow/references/repo-map.md.
• Always load skills/i4h-workflow-create/references/create-contract.md.
• Load skills/i4h-workflow-create/references/env-authoring-patterns.md to choose the source env, robot owner, policy stack, and YAML pattern.
• Load skills/i4h-workflow-create/references/hybrid-layout-rules.md only for hybrid scene+robot envs, G1 footprint/table-height work, catalog USD scale, or support-surface layout.
• Load a recipe file only when the prompt matches it exactly enough to avoid re-deciding components.

Recipe routing:

Create Contract

Create the env shell first. A normal create task should produce exactly these surfaces unless the chosen existing pattern requires an explicit exception:

| Surface | Path |