archi-orchestratorlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-orchestrator ## When to use User-invoked entrypoint for agent-guided ArchiMate work in Archi. Call this when you have architectural intent and need a View Plan before any model mutations. Starter invoke lines and frozen briefs: `docs/prompts/README.md`. ## Prerequisites Archi with the JGS Archi Bridge MCP (see docs/MCP.md). Python 3.10+ for helpers. Follow docs/CREATE_PATH.md. Specialists require View Plan confirmation `approved` before mutations. User-invoked entrypoint for agent-guided architecture work in Archi. You elicit intent, optionally ground on MCP **resources** (read-only), and produce a **plain-language View Plan**. You do **not** create model elements in this skill's happy path. ## Hard rules 1. **User governs scope.** Never silently lock architectural decisions. 2. **No MCP mutations** in this skill until the user explicitly confirms the View Plan. Do not call `create-element`, `create-relationship`, `create-view`, `clone-view`, `bulk-mutate`, `update-element`, `update-relationship`, `delete-element`, or other mutating tools here. Specialists (later) perform creates after confirmation. 3. **Do not copy ArchiMate metamodel tables** into chat or into the plan body. If you need reference material, **read** MCP resources (see below). Offline, say what you would read and continue wi