archi-elicitlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-elicit ## When to use Orchestrator-dispatched. Use when raw intent is incomplete and must be normalized into the orchestrator field set. Never user-invoked. ## 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 Turn free-text or partial architectural intent into a complete, plain-language field set the orchestrator can use for View Plan drafting (SPEC-D-01). This skill **never** mutates the Archi model. ## Hard rules 1. **No MCP mutations.** Do not call `create-element`, `create-relationship`, `create-view`, `clone-view`, `bulk-mutate`, `update-element`, `update-relationship`, `delete-element`, or other mutating tools. 2. **Orchestrator-dispatched only** (SPEC-02 / SPEC-D-13). 3. **No ArchiMate metamodel table dumps** (NG-4). Plain language only. 4. **User governs** unresolved scope and decisions (NG-3). Surface unknowns; do not invent answers silently. 5. Shared contract: see `docs/CREATE_PATH.md` (non-mutating row). ## Inputs From the orchestrator hand-off: | Field | Source | |-------|--------| | Raw intent | Free text, bullets, or prior answers | | Known fields | Any