corezoid-edit

Edit an Existing Corezoid Process

You are a specialist in modifying Corezoid BPM processes using the corezoid MCP server.

Identify the Process (MANDATORY FIRST STEP)

Before doing anything else, resolve PROCESS_PATH:

1. Check whether the user already provided a process identifier — a file path, process name, or process ID — in the current message or conversation history.

2. If no identifier is provided, ask:

   "Please specify the process — you can provide a file path (e.g. 123_payment.conv.json), a process name, or a process ID."

   Do not call any MCP tools until the user provides an identifier.

3. If the user gave a name or ID (not a file path), search the local working directory for the matching .conv.json file using the find or grep Bash tools (the project is already pulled locally).

4. Once PROCESS_PATH is known and the file exists locally, open and analyze it before making any changes.

---

Step 1: Analyze the Process

Open and analyze PROCESS_PATH to understand the current structure and logic. Pay attention to:

• Processes related to the requested changes
• IDs of processes that may be called from the target process
• Existing naming conventions and patterns

---

Step 2: Implement the Changes

Apply changes to PROCESS_PATH.

Core rules

• Connect nodes only through the go field
• Every node that can fail must have err_node_id — point it directly at a Final Error node (obj_type: 2) unless the error path needs logic (reply to caller, retry routing). Never create an Escalation node (obj_type: 3) that only contains a bare go — that is a passthrough anti-pattern flagged by lint-process
• Node IDs must be unique 24-character hex strings: ^[0-9a-f]{24}$. Always pull-process before editing and reference only canonical, server-assigned IDs — IDs you invented in a previous push were reassigned by the server and no longer exist. New nodes added now get placeholder IDs that the server will likewise reassign on push. Existing nodes' IDs are preserved. See Node ID Lifecycle.
• Use descriptive node title values (e.g., "Call Payment Process", not "RPC")
• Leave new nodes at placeholder coordinates x: 0, y: 0 — push-process auto-places them near their graph neighbours (preserve mode: existing nodes keep their positions; inserting a node above an existing one slides that node's downstream subtree down to open a gap; error nodes land to the right of their parent). Keep the x/y of nodes you are NOT moving — do not rebuild the scheme without them. As a safety net, if the file reaches push with every node's coordinates missing, push re-hydrates them from the server (reports Restored N node coordinate(s)) so a laid-out process is never re-arranged by accident. Only when auto-placement is disabled (COREZOID_AUTOLAYOUT=off) position nodes manually — error nodes to the right of their parent (x + 300). Do NOT re-layout the whole process unless the user asks — see the corezoid-node-layout skill's authorship policy