workflow-assistant

Workflow Assistant

Use this skill when a user wants help with a live ComfyUI workflow, saved workflow JSON, generated image metadata, custom node graph, or FL-MCP tool session.

This skill is workflow-first. It borrows the old Ren Agent's operating discipline and cognitive modes, but does not adopt a persona, product UI, hosted chat runtime, or ren:// links.

Core Loop

1. Compile the whole requested graph change once.
   • For a whole-branch request such as find, jump, compare, clone, replace, or remove, call workflow_branches_discover first. Use exact returned workflow, graph, catalog, scope, branch, node, slot, and boundary-edge facts; never authorize a branch from its label or fingerprint.
   • Resolve comparison operands to two exact branch IDs under the same pinned catalog. One bounded listing may identify both uniquely; otherwise perform separate pinned discovery resolutions. Never guess two branches from one ambiguous text query.
   • For whole-branch clone, replace, or remove, pass the exact discovery pins and mappings to compile_workflow_branch_operation. Root operations return GraphPatch v2; supported nested operations return scoped GraphPatch v3.
   • For a new workflow, an added branch, a rewire, a removal, or another explicit topology change, call compile_workflow_refinement_spec first. Mask pixels and prompt text use their dedicated narrow lanes below; do not send value-only prompt edits through GraphPatch.
   • Include every requested role or exact class, value, edge, update/removal, attachment, and layout hint in one semantic request.
   • Describe the desired endpoints rather than guessing intermediary classes or dynamic dotted paths. The compiler prefers direct compatibility, then may infer a unique bounded supported local converter route. Partner/API/heavy/output nodes require explicit intent.
   • When the user says exactly, only, or no extra nodes, set allow_inferred_converters=false.
   • Use deterministic existing-node selectors. Set selected=true when the user says “selected”, “this”, or “that”; the compiler reads the live selection internally.
   • Do not precede the compiler with workflow JSON, overview, selection, node search/details, slots, values, or layout reads. It reads the active graph (including an empty canvas) and refreshed local native, partner, and custom schemas internally.
2. Respect deterministic outcomes.
   • If valid=true, pass the returned apply_request unchanged to apply_workflow_graph_patch.
   • After a successful whole-branch apply, call resolve_workflow_branch_successor with the unchanged apply envelope, compiler pending_successor_locator, and the apply result's exact aliases, workflow identity, and final graph hash. Treat its per-scope successor list as authoritative; zero or multiple successors are valid outcomes when explicitly attested.
   • If needs_choice=true, show the ranked node, endpoint, or route candidates and wait for the user. Never accept an alphabetical tie-break.
   • If a schema is classified unsupported, stop and report it. Use lower-level schema tools only in a focused diagnostic follow-up, never to bypass the failed atomic route in the same run.
3. Apply one atomic GraphPatch.
   • Keep the same application ID for retries so the idempotency ledger cannot duplicate work.
   • Root GraphPatch v2 and scoped GraphPatch v3 may create, update, connect, disconnect, remove, attach, and lay out arbitrary acyclic branches with fan-in, fan-out, multiple sinks, dynamic inputs, and explicit widget-to-input conversion.
   • It pins workflow, graph, catalog, and schemas; preserves unrelated state; visibly applies mutations in deterministic order; verifies the exact final graph; fully rolls back on failure; and never queues.
   • Do not fall back to create_nodes, set_node_values, connect_nodes_batch, remove_nodes, or the legacy compile_workflow_spec/resolve_workflow_spec/plan_workflow/apply_workflow_plan compilers after a GraphPatch validation/application failure.
4. Trust exact verification.
   • A successful application already verifies the graph, node facts, attachments, layout, and unrelated workflow envelope. Do not add redundant overview/JSON/slot/value/layout reads.
   • Inspect again only when the result reports a mismatch, the user explicitly asks for a visual check, or a later execution/output review requires it.
5. Queue only after validation.
   • Check required sampler, decoder, loader, and save connections.
   • After queueing, inspect queue/history/errors before declaring success.