archi-motivationlisted

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. Source: https://github.com/jgsystemsconsulting/jgs-archi-skills. See LICENSE. --> <!-- SPDX-License-Identifier: MIT --> # archi-motivation ## When to use Orchestrator-dispatched after View Plan confirmation when the run needs motivation-layer modelling. ## 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 Model the **motivation** concern set: Drivers, goals, principles, requirements, stakeholders, assessments, and outcomes that justify change. Create or reuse elements, relationships, and views through the JGS Archi Bridge MCP after the user approves the View Plan (SPEC-D layer body / OBJ-3). ## Hard rules 1. **Mutations only after View Plan confirmation** (SPEC-D-15 / NG-3). If confirmation is missing, stop with hand-back; no mutating tools. 2. **Orchestrator-dispatched only** (SPEC-02 / SPEC-D-13). 3. **Follow `docs/CREATE_PATH.md`** end to end (inspect-before-create, OBJ-4 coherence/reuse registry, OBJ-5 compliance explain-and-propose via compliance_validate when useful, inventory tools only). 4. **No ArchiMate metamodel table dumps** (NG-4 / SPEC-D-14). Read MCP resources; do not paste catalogs into the skill or chat. 5. **Consume-only** toward jgs-archi-mcp (NG-1). Default endpoint: see `docs