jgs-archi-skills modelling run

jgs-archi-skills modelling run A workflow diagram generated by Archify. 01 / User 02 / Orchestrator EX / Confirmation 04 / Specialists + Archi Intake Plan + ground Confirm Model in Archi View Plan User gate Write via MCP User · plain-language intent · User › Intake User plain-language intent archi-orchestrator · elicit + View Plan · Orchestrator › View Plan › Intake · user-invoked archi-orchestrator elicit + View Plan user-invoked elicit + viewpoint-select · stakeholder, concern, purpose · Orchestrator › View Plan › Plan + ground elicit + viewpoint-select stakeholder, concern, purpose Confirmation Gate · approve / revise / abort · Confirmation › User gate › Confirm · no mutations yet Confirmation Gate approve / revise / abort no mutations yet Revise or abort · user decision · Confirmation › User gate › Model in Archi Revise or abort user decision Layer specialists · motivation to migration · Specialists + Archi › Write via MCP › Model in Archi Layer specialists motivation to migration Trace, QA, layout, docs · write into Archi via MCP · Specialists + Archi › Write via MCP › Model in Archi · Archi canvas Trace, QA, layout, docs write into Archi via MCP Archi canvas approved revise or abort draft View Plan grounded viewpoints intent revise plan trace then close Legend Agent logic Policy Cloud service External system

Two entrypoints

  • • Fourteen skills. Modelling invoke: /archi-orchestrator. Pack defects: /jgs-upstream-feedback.
  • • Specialists are dispatched after the View Plan is approved

User governs

  • • No create-element or other MCP mutations until you confirm
  • • Revise returns to the orchestrator; abort ends the run

Archi is the canvas

  • • Skills consume the JGS Archi Bridge MCP on loopback
  • • Rationale is written into the model, not a second diagramming tool