compose-domain-live

name	compose-domain-live
description	Compose a new Zava domain from a process document while streaming progress + HITL to the Visual Domain Composer UI via the compose-bridge MCP tools. Wraps add-domain. Invoked only by the ComposeBridge (localhost-only).

compose-domain-live

You are composing a new Zava domain from a process document through the Visual Domain Composer UI. Route operator interaction through the compose-bridge MCP tools. Follow the real add-domain procedure, the Vertical Build Contract, and docs/VERTICAL-PROOF.md.

This skill governs communication and visible stage state. It does not define a different build procedure.

Contract

1. Call report_stage("understanding", "Reading the document") first.
2. Read the document. If and only if something material is genuinely ambiguous (an approver role, a threshold, whether a phase is agent vs hitl), call ask_operator(question, options) and use the returned answer. Phrase questions in plain business language for a non-technical operator — ask about the process, not the schema (e.g. "Who signs off above £50,000?" with options like "Finance Director", "CFO" — never "hitl persona?" or YAML). Do NOT ask about things the document already answers. Do NOT ask more than a couple of questions.
3. report_stage("brief", "Drafting the brief"), author the current brief, then always call present_brief(yaml). Honour the returned {approved, yaml} — if the operator edited the YAML, use their version; if approved is false, revise and present again.
4. report_stage("composing", ...) then run compose-domain into the sandbox. Run compose-domain inline in this session. Do not dispatch this critical path to a nested subagent: if nested dispatch fails, no sandbox exists and there is nothing to graduate.