메뉴
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).
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/arturcrmbot/zava-control-plane --skill compose-domain-live명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Sub-skill of `compose-domain`. Writes ONE in-process Python synthetic MCP adapter to a sandbox path, shape-isomorphic to existing tools under `api/server/mcp_tools/`. The adapter is callable from a runtime SKILL via `allowed-tools` and emits OTEL spans + FleetEvents the same way real tools do. Returns deterministic synthetic data — no real backend. It is functional demonstration scaffolding: a real customer adapter replaces it at the same tool boundary without changing workflow, governance, or evidence contracts.
Current design-time meta-skill. Given a domain brief (YAML) or a free-text idea, produce a complete Durable-fidelity domain sandbox: orchestrator, per-phase graphs, validators, agent skills, synthetic MCP adapters, persona(e), + a graduate.sh script that mechanically wires everything into the live trees. The current contract encodes: durable.* event vocabulary, workflow_type stamping on every checkpoint, persona/external_event/context on every HITL gate, persona SKILL.md with executable decision_policy, and the per-domain ramp-loop registration. Every generated domain inherits the contract by construction. Sandbox-only; never touches real trees directly. Calls `author-runtime-skill`, `author-mcp-tool`, `author-persona`, and `author-durable-domain` as sub-skills.
Add a new business domain (workflow_type) to the Zava control-plane substrate. Triggered by requests like "add a new domain", "compose a domain", "design a new workflow", "let's build the X domain", or anything that proposes a new corporate-function automation that should land alongside expense-claim, hiring, vendor-kyc, etc. End-to-end recipe: brief → compose-domain sandbox → graduate.sh → validate active pack → VERTICAL-PROOF.md.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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). |
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.
report_stage("understanding", "Reading the document") first.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.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.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.report_stage("graduating", ...) then run the generated graduate.sh.
Graduation must be complete and pack-scoped; do not apply an undocumented
manual patch list.report_stage("verifying", ...) then run the active-pack, runtime, and
execution-visibility gates referenced by add-domain.
Include compose-domain CHECKLIST §12: live authority closure, persisted
HITL recovery context, persona/Durable resume timing, and browser event
recovery across a lower latest_seq. If a check fails, fix it and
re-verify — narrate what you're doing.
Also enforce the blocking execution-visibility gate: actual execution
evidence must be visible and self-consistent for every active non-stub
workflow type. Validate observed evidence rather than predicting conditional
branches. Generated agents use run_agent_session; run the live/replay
tools/workflow_visibility_proof.py commands from compose-domain CHECKLIST
§13.composition_complete(workflow_type, display_name) after the
sandbox exists, graduation completed, the active pack contains the new
workflow_type, and every verification gate above passed. A missing sandbox
or failed verification is a failure: report the exact error and stop. Never
report the domain as ready when it was not built. Do not restart the server
yourself — the UI's Ignite control handles the restart.Normal assistant messages may briefly explain current stage and evidence. Do not expose hidden chain-of-thought or replace artifact state with optimistic narration. The UI's Ignite control owns server restart.