archi-layoutlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-layout ## When to use Orchestrator-dispatched after View Plan confirmation when target views need Archi-native layout and presentation. ## 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. Orchestrator-dispatched specialist. Not a primary user entrypoint. ## Purpose Improve readability of target Archi views using inventory layout and presentation tools only (SPEC-D-10). Archi is the only canvas (NG-2). ## Hard rules 1. **Mutations only after View Plan confirmation** (SPEC-D-15). 2. **Orchestrator-dispatched only** (SPEC-02). 3. **Follow `docs/CREATE_PATH.md`**. 4. **No alternate renderer** (NG-2). No non-Archi export as the primary layout path. 5. Inventory layout tool names only. ## Inputs | Field | Required | Notes | |-------|----------|-------| | Confirmation status | yes | approved | | Target view IDs/names | yes | | | Readability goals | optional | fewer crossings, group by layer, spacing | ## MCP resources - `archimate://recipes/index` - `archimate://reference/archimate-view-patterns` - `archimate://prompts/routing-preconditions-checklist` ## MCP tools Assess: `assess-layout`, `get-view-contents`, `detect-hub-elements`, `export-view` La