/hep-build

description: Build, repair, or package Agentlas agents and teams with Hephaestus.
argument-hint: '[ontology|single-agent|team|package] [details...]'
allowed-tools: Bash, Read, Glob, Grep

Update fallback: 자동 업데이트가 안 되면 `hephaestus update`를 한 번 실행하세요. 업데이트하지 않아도 현재 버전 명령은 그대로 동작합니다.

/hep-build

Raw arguments: `$ARGUMENTS`

Use Hephaestus as the Agentlas builder surface:

• create a new single agent
• create a multi-agent team
• package an existing Claude/Codex/Gemini workspace into Agentlas architecture
• repair generated Agentlas command files
• open `ontology` as the Knowledge/Memory panel

Expose this as the only public build command, next to `/hep-network` and `/hep-cloud`. Do not advertise internal support skills as commands.

Route

If the first argument is `ontology`, open the project-local ontology GUI:

1. Find the first executable path from the shell snippet below. 2. Run:

RUNNER=""
CODEX_HOME_DIR="${CODEX_HOME:-$HOME/.codex}"
for candidate in \
  "$HOME/.agentlas/runtime/current/bin/hephaestus" \
  "${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/bin/hephaestus}" \
  "${CODEX_PLUGIN_ROOT:+$CODEX_PLUGIN_ROOT/bin/hephaestus}" \
  "${PLUGIN_ROOT:+$PLUGIN_ROOT/bin/hephaestus}" \
  "./bin/hephaestus" \
  "./claude/plugins/agentlas-core-engine-meta-agent/bin/hephaestus" \
  "./codex/plugins/agentlas-core-engine-meta-agent/bin/hephaestus"
do
  if [ -n "$candidate" ] && [ -x "$candidate" ]; then
    RUNNER="$candidate"
    break
  fi
done
if [ -z "$RUNNER" ]; then
  for cache in "$HOME/.claude/plugins/cache/agentlas-core-engine/hephaestus" \
               "${CODEX_HOME:-$HOME/.codex}/plugins/cache/agentlas-core-engine/hephaestus"; do
    newest="$(ls -d "$cache"/*/bin/hephaestus 2>/dev/null | sort -V | tail -1)"
    if [ -n "$newest" ] && [ -x "$newest" ]; then RUNNER="$newest"; break; fi
  done
fi
if [ -z "$RUNNER" ]; then
  echo "Hephaestus runtime not found. Run the installer first." >&2
  exit 1
fi
"$RUNNER" ontology --gui .

3. Report the returned `gui_url`, `db_path`, `inbox_path`, and verification status.

If the first argument is not `ontology`, route to the Agentlas Core Engine Meta-Agent team.

**Step 0 — resolve the engine root, and read the engine's own contracts from it.** Every path in steps 1, 2 and 4 belongs to Hephaestus, not to the user's project. Read relatively and in someone else's repository you find nothing — or worse, you find their `AGENTS.md` and follow it. Measured 2026-08-07: three packages built outside this engine's own repository shipped 5 of 18 required artifacts, because these reads silently returned nothing and the model improvised the rest.

The marker is `AGENTS.md` **and** `package-contract.json` together. The installed runtime root carries the contract and the code but not the instructions — those travel in its `host_adapters/` bundle — so testing for the contract alone selects a root where every read in steps 1, 2 and 4 comes back empty.

ENGINE=""
for candidate in \
  "${CLAUDE_PLUGIN_ROOT:-}" \
  "${CODEX_PLUGIN_ROOT:-}" \
  "${PLUGIN_ROOT:-}" \
  "$HOME/.agentlas/runtime/current/host_adapters/claude/plugins/agentlas-core-engine-meta-agent" \
  "$HOME/.agentlas/runtime/current/host_adapters/codex/plugins/agentlas-core-engine-meta-agent" \
  "$HOME/.agentlas/runtime/current" \
  "."
do
  if [ -n "$candidate" ] && [ -f "$candidate/AGENTS.md" ] && [ -f "$candidate/package-contract.json" ]; then
    ENGINE="$candidate"; break
  fi
done
[ -z "$ENGINE" ] && { echo "Hephaestus engine not found. Run the installer first." >&2; exit 1; }
echo "ENGINE=$ENGINE"

Report the resolved `ENGINE` in the final `evidence`. If a file below is missing from it, say so as a blocker — do not carry on and improvise it.

1. Read `$ENGINE/AGENTS.md`. 2. Read `$ENGINE/.agentlas/mode-map.json` and the mode contract it names under `$ENGINE/modes/`. 3. Classify the request as single-agent builder, multi-agent team builder, or packager by independent ownership boundaries: one role owning memory/context, tools/permissions, and success criteria is single-agent; two or more such roles plus routing/synthesis/handoff is team-builder; existing material repair/conversion is packager. If single↔multi is unclear, ask first in plain language: "이 일을 한 명의 전문가가 처음부터 끝까지 맡으면 되나요, 아니면 조사/분석/검토처럼 여러 전문가가 나눠 맡고 마지막에 합쳐야 하나요?" Do not show non-technical users internal labels like ownership boundary, memory/context, synthesis, or produces/consumes. 4. Run the Builder Interview and Research Gate in `$ENGINE/docs/builder-interview-research-gate.md` before writing substantial package files. Ask an 8-12 question first batch when the request is vague; continue follow-ups until target user, tasks, inputs, outputs, examples, tools/plugins, memory, failure modes, ownership boundaries, execution order, and evals are clear. Question selection, ambiguity scoring and the stop decision follow the briefing interview engine (`agentlas_cloud/interview/`): lens-table questions (anti_scope / done_signal / stop_criterion are required), stop only at ambiguity <= 0.2 with all dimension floors met for 2 consecutive rounds, then one coverage check plus a one-sentence goal restate. Research official or primary docs, similar agent repositories or comparables, GitHub examples, academic/professional theory, and tool/plugin docs. Record selected and rejected tools/plugins with permission, secret, fallback, and smoke-test notes, then synthesize domain-expert behavior before writing prompts. 5. **Lay the contract down before writing anything.** Set `PACKAGE_ROOT` to the absolute path of the package folder, then:

   "$ENGINE/bin/hephaestus" contract scaffold "$PACKAGE_ROOT" --mode single|team|package

Then, as soon as the routing card exists, let the engine answer every hole it can from the package's own declarations:

   "$ENGINE/bin/hephaestus" contract complete "$PACKAGE_ROOT"