From 9ff20529a53b1743762fce7b0800f8adc56d49c9 Mon Sep 17 00:00:00 2001 From: tractorjuice <129532814+tractorjuice@users.noreply.github.com> Date: Sat, 16 May 2026 10:55:16 +0000 Subject: [PATCH] chore(converter): sync drift across all extension formats MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Re-runs scripts/converter.py to bring arckit-codex / arckit-opencode / arckit-gemini / arckit-copilot / arckit-paperclip back in sync with the plugin source. Drift had accumulated since the last bulk regeneration. Picked up: - Version bump 4.20.3 → 4.21.0 in arckit-codex plugin.json (and matching commands.json bump in arckit-paperclip). - arckit-framework command + agent: removed reference to the now- generated (not template-backed) executive guide. - arckit-uae-priorities-alignment: upstream command-file edit. - Skill SKILL.md regenerations for architecture-workflow, mermaid-syntax, plantuml-syntax, wardley-mapping. - custom-commands guide regenerated across docs/guides/ mirrors. No source-of-truth files (in arckit-claude/) touched in this commit — this is pure mechanical re-propagation of changes that were already on main. Co-Authored-By: Claude Opus 4.7 (1M context) --- arckit-codex/.codex-plugin/plugin.json | 2 +- arckit-codex/agents/arckit-framework.md | 2 +- arckit-codex/agents/arckit-framework.toml | 2 +- arckit-codex/commands/arckit.framework.md | 2 +- arckit-codex/commands/arckit.uae-priorities-alignment.md | 2 +- arckit-codex/docs/guides/custom-commands.md | 7 +++---- arckit-codex/prompts/arckit.framework.md | 2 +- arckit-codex/prompts/arckit.uae-priorities-alignment.md | 2 +- arckit-codex/skills/architecture-workflow/SKILL.md | 9 ++++++--- arckit-codex/skills/arckit-framework/SKILL.md | 2 +- .../skills/arckit-uae-priorities-alignment/SKILL.md | 2 +- arckit-codex/skills/mermaid-syntax/SKILL.md | 2 ++ arckit-codex/skills/plantuml-syntax/SKILL.md | 2 ++ arckit-codex/skills/wardley-mapping/SKILL.md | 2 ++ arckit-copilot/agents/arckit-framework.agent.md | 2 +- arckit-copilot/docs/guides/custom-commands.md | 7 +++---- .../prompts/arckit-uae-priorities-alignment.prompt.md | 2 +- arckit-copilot/skills/architecture-workflow/SKILL.md | 9 ++++++--- arckit-copilot/skills/mermaid-syntax/SKILL.md | 2 ++ arckit-copilot/skills/plantuml-syntax/SKILL.md | 2 ++ arckit-copilot/skills/wardley-mapping/SKILL.md | 2 ++ arckit-gemini/agents/arckit-framework.md | 2 +- arckit-gemini/commands/arckit/framework.toml | 2 +- arckit-opencode/agents/arckit-framework.md | 2 +- arckit-opencode/commands/arckit.framework.md | 2 +- .../commands/arckit.uae-priorities-alignment.md | 2 +- arckit-opencode/docs/guides/custom-commands.md | 7 +++---- arckit-opencode/skills/architecture-workflow/SKILL.md | 9 ++++++--- arckit-opencode/skills/mermaid-syntax/SKILL.md | 2 ++ arckit-opencode/skills/plantuml-syntax/SKILL.md | 2 ++ arckit-opencode/skills/wardley-mapping/SKILL.md | 2 ++ arckit-paperclip/docs/guides/custom-commands.md | 7 +++---- arckit-paperclip/skills/architecture-workflow/SKILL.md | 9 ++++++--- arckit-paperclip/skills/mermaid-syntax/SKILL.md | 2 ++ arckit-paperclip/skills/plantuml-syntax/SKILL.md | 2 ++ arckit-paperclip/skills/wardley-mapping/SKILL.md | 2 ++ arckit-paperclip/src/data/commands.json | 4 ++-- 37 files changed, 78 insertions(+), 46 deletions(-) diff --git a/arckit-codex/.codex-plugin/plugin.json b/arckit-codex/.codex-plugin/plugin.json index 43ed7908..894554c9 100644 --- a/arckit-codex/.codex-plugin/plugin.json +++ b/arckit-codex/.codex-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "arckit-codex", - "version": "4.20.3", + "version": "4.21.0", "description": "Enterprise architecture governance, procurement, research, and delivery workflows for Codex.", "author": { "name": "ArcKit", diff --git a/arckit-codex/agents/arckit-framework.md b/arckit-codex/agents/arckit-framework.md index 81aac85b..0afc3ff0 100644 --- a/arckit-codex/agents/arckit-framework.md +++ b/arckit-codex/agents/arckit-framework.md @@ -248,7 +248,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-codex/agents/arckit-framework.toml b/arckit-codex/agents/arckit-framework.toml index 7f0f6b04..cc291bc1 100644 --- a/arckit-codex/agents/arckit-framework.toml +++ b/arckit-codex/agents/arckit-framework.toml @@ -205,7 +205,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-codex/commands/arckit.framework.md b/arckit-codex/commands/arckit.framework.md index 353bc4af..56df939e 100644 --- a/arckit-codex/commands/arckit.framework.md +++ b/arckit-codex/commands/arckit.framework.md @@ -203,7 +203,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-codex/commands/arckit.uae-priorities-alignment.md b/arckit-codex/commands/arckit.uae-priorities-alignment.md index b529201f..b824c819 100644 --- a/arckit-codex/commands/arckit.uae-priorities-alignment.md +++ b/arckit-codex/commands/arckit.uae-priorities-alignment.md @@ -16,7 +16,7 @@ You are an enterprise architect generating a National Priorities Alignment State 1. Read prerequisites: - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present) - - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present) + - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present) - `.arckit/templates/_partials/RENDERING.md` 2. Read the template: - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override) diff --git a/arckit-codex/docs/guides/custom-commands.md b/arckit-codex/docs/guides/custom-commands.md index 05eecf3e..18e0ea7d 100644 --- a/arckit-codex/docs/guides/custom-commands.md +++ b/arckit-codex/docs/guides/custom-commands.md @@ -133,10 +133,9 @@ $ARGUMENTS ## Instructions -1. **Read the template** (with user override support): - - **First**, check if `.arckit/templates/sla-template.md` exists in the project root - - **If found**: Read the user's customised template - - **If not found**: Read `${CLAUDE_PLUGIN_ROOT}/templates/sla-template.md` (default) +1. **Read the template**: + - Read `.arckit/templates/sla-template.md` from the project root. + - If the file is missing, stop and ask the user to create it (custom commands ship their template alongside the command). 2. **Read the project requirements**: - Locate `projects//ARC--REQ-v*.md` diff --git a/arckit-codex/prompts/arckit.framework.md b/arckit-codex/prompts/arckit.framework.md index 353bc4af..56df939e 100644 --- a/arckit-codex/prompts/arckit.framework.md +++ b/arckit-codex/prompts/arckit.framework.md @@ -203,7 +203,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-codex/prompts/arckit.uae-priorities-alignment.md b/arckit-codex/prompts/arckit.uae-priorities-alignment.md index b529201f..b824c819 100644 --- a/arckit-codex/prompts/arckit.uae-priorities-alignment.md +++ b/arckit-codex/prompts/arckit.uae-priorities-alignment.md @@ -16,7 +16,7 @@ You are an enterprise architect generating a National Priorities Alignment State 1. Read prerequisites: - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present) - - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present) + - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present) - `.arckit/templates/_partials/RENDERING.md` 2. Read the template: - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override) diff --git a/arckit-codex/skills/architecture-workflow/SKILL.md b/arckit-codex/skills/architecture-workflow/SKILL.md index 2b75a2be..659e209a 100644 --- a/arckit-codex/skills/architecture-workflow/SKILL.md +++ b/arckit-codex/skills/architecture-workflow/SKILL.md @@ -1,8 +1,11 @@ --- name: architecture-workflow -description: This skill should be used when the user asks how to start an architecture - project, which ArcKit commands to run and in what order, what workflow to follow, - getting started, new project setup, guide me through, or what comes next. +description: This skill should be used when the user is starting an architecture project + or asking what to run next. Load whenever the task sounds like 'I'm starting a new + project', 'guide me through', 'what command should I run', 'what comes next', 'how + do I begin', 'help me get started', 'which $arckit-* in what order', 'set up a new + project', 'new system build', or 'where do I start'. Recommends a tailored command + sequence based on sector, project type, current stage, and timeline. --- # Architecture Workflow diff --git a/arckit-codex/skills/arckit-framework/SKILL.md b/arckit-codex/skills/arckit-framework/SKILL.md index b910d8ce..ce89f2b3 100644 --- a/arckit-codex/skills/arckit-framework/SKILL.md +++ b/arckit-codex/skills/arckit-framework/SKILL.md @@ -204,7 +204,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `$arckit-navigator` (project coverage) · `$arckit-traceability` (cross-reference validation) · `$arckit-strategy` (executive synthesis) diff --git a/arckit-codex/skills/arckit-uae-priorities-alignment/SKILL.md b/arckit-codex/skills/arckit-uae-priorities-alignment/SKILL.md index 05eb1ac7..ad058a7c 100644 --- a/arckit-codex/skills/arckit-uae-priorities-alignment/SKILL.md +++ b/arckit-codex/skills/arckit-uae-priorities-alignment/SKILL.md @@ -17,7 +17,7 @@ You are an enterprise architect generating a National Priorities Alignment State 1. Read prerequisites: - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present) - - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present) + - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present) - `.arckit/templates/_partials/RENDERING.md` 2. Read the template: - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override) diff --git a/arckit-codex/skills/mermaid-syntax/SKILL.md b/arckit-codex/skills/mermaid-syntax/SKILL.md index 7eefde2e..cf1021e1 100644 --- a/arckit-codex/skills/mermaid-syntax/SKILL.md +++ b/arckit-codex/skills/mermaid-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Mermaid diagram A comprehensive reference for all 23 Mermaid diagram types plus configuration and theming. This skill provides official Mermaid syntax documentation sourced from the [mermaid-skill](https://github.com/WH-2099/mermaid-skill) project (auto-synced from upstream Mermaid docs). +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are Mermaid syntax docs, not commands. + To look up syntax for a specific diagram type, identify the type from the table below and read the corresponding reference file. ## Supported Diagram Types diff --git a/arckit-codex/skills/plantuml-syntax/SKILL.md b/arckit-codex/skills/plantuml-syntax/SKILL.md index 094e8efb..498b6e8e 100644 --- a/arckit-codex/skills/plantuml-syntax/SKILL.md +++ b/arckit-codex/skills/plantuml-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about PlantUML syntax A comprehensive reference for PlantUML diagram types with a focus on C4-PlantUML for architecture diagrams. This skill provides syntax documentation adapted from the [SpillwaveSolutions/plantuml](https://github.com/SpillwaveSolutions/plantuml) project, supplemented with ArcKit-specific C4 layout conflict rules and best practices. +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are PlantUML/C4 syntax docs, not commands. + ## Supported Diagram Types Select the appropriate diagram type and read the corresponding reference file: diff --git a/arckit-codex/skills/wardley-mapping/SKILL.md b/arckit-codex/skills/wardley-mapping/SKILL.md index c09022c7..a5195313 100644 --- a/arckit-codex/skills/wardley-mapping/SKILL.md +++ b/arckit-codex/skills/wardley-mapping/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Wardley Mapping, A strategic mapping technique created by Simon Wardley for understanding competitive landscape, technology evolution, and making informed architectural decisions. A Wardley Map visualizes four dimensions: the **value chain** (components needed to meet user needs), **evolution** (how components mature over time), the **landscape** (competitive environment), and **movement** (how the landscape changes). +**This skill ships reference material, not runnable scripts.** Read the relevant section here (or the linked references) with `Read`, apply the OnlineWardleyMaps syntax, and write the map into the user's artefact. Do not `Bash`-execute anything from this skill — there is no script to run. + ## Map Structure The following diagram illustrates the conceptual axes of a Wardley Map. For the generation template with placeholders, see the Map Template section below. diff --git a/arckit-copilot/agents/arckit-framework.agent.md b/arckit-copilot/agents/arckit-framework.agent.md index 1a9545f6..e3cb2e0c 100644 --- a/arckit-copilot/agents/arckit-framework.agent.md +++ b/arckit-copilot/agents/arckit-framework.agent.md @@ -215,7 +215,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-copilot/docs/guides/custom-commands.md b/arckit-copilot/docs/guides/custom-commands.md index 05eecf3e..18e0ea7d 100644 --- a/arckit-copilot/docs/guides/custom-commands.md +++ b/arckit-copilot/docs/guides/custom-commands.md @@ -133,10 +133,9 @@ $ARGUMENTS ## Instructions -1. **Read the template** (with user override support): - - **First**, check if `.arckit/templates/sla-template.md` exists in the project root - - **If found**: Read the user's customised template - - **If not found**: Read `${CLAUDE_PLUGIN_ROOT}/templates/sla-template.md` (default) +1. **Read the template**: + - Read `.arckit/templates/sla-template.md` from the project root. + - If the file is missing, stop and ask the user to create it (custom commands ship their template alongside the command). 2. **Read the project requirements**: - Locate `projects//ARC--REQ-v*.md` diff --git a/arckit-copilot/prompts/arckit-uae-priorities-alignment.prompt.md b/arckit-copilot/prompts/arckit-uae-priorities-alignment.prompt.md index f9e0ec4e..34c5d368 100644 --- a/arckit-copilot/prompts/arckit-uae-priorities-alignment.prompt.md +++ b/arckit-copilot/prompts/arckit-uae-priorities-alignment.prompt.md @@ -18,7 +18,7 @@ You are an enterprise architect generating a National Priorities Alignment State 1. Read prerequisites: - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present) - - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present) + - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present) - `.arckit/templates/_partials/RENDERING.md` 2. Read the template: - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override) diff --git a/arckit-copilot/skills/architecture-workflow/SKILL.md b/arckit-copilot/skills/architecture-workflow/SKILL.md index 4fb258a9..9ac4fa79 100644 --- a/arckit-copilot/skills/architecture-workflow/SKILL.md +++ b/arckit-copilot/skills/architecture-workflow/SKILL.md @@ -1,8 +1,11 @@ --- name: architecture-workflow -description: This skill should be used when the user asks how to start an architecture - project, which ArcKit commands to run and in what order, what workflow to follow, - getting started, new project setup, guide me through, or what comes next. +description: This skill should be used when the user is starting an architecture project + or asking what to run next. Load whenever the task sounds like 'I'm starting a new + project', 'guide me through', 'what command should I run', 'what comes next', 'how + do I begin', 'help me get started', 'which /arckit:* in what order', 'set up a new + project', 'new system build', or 'where do I start'. Recommends a tailored command + sequence based on sector, project type, current stage, and timeline. --- # Architecture Workflow diff --git a/arckit-copilot/skills/mermaid-syntax/SKILL.md b/arckit-copilot/skills/mermaid-syntax/SKILL.md index ff0edba0..3e001a4b 100644 --- a/arckit-copilot/skills/mermaid-syntax/SKILL.md +++ b/arckit-copilot/skills/mermaid-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Mermaid diagram A comprehensive reference for all 23 Mermaid diagram types plus configuration and theming. This skill provides official Mermaid syntax documentation sourced from the [mermaid-skill](https://github.com/WH-2099/mermaid-skill) project (auto-synced from upstream Mermaid docs). +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are Mermaid syntax docs, not commands. + To look up syntax for a specific diagram type, identify the type from the table below and read the corresponding reference file. ## Supported Diagram Types diff --git a/arckit-copilot/skills/plantuml-syntax/SKILL.md b/arckit-copilot/skills/plantuml-syntax/SKILL.md index 57365269..4dff9df0 100644 --- a/arckit-copilot/skills/plantuml-syntax/SKILL.md +++ b/arckit-copilot/skills/plantuml-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about PlantUML syntax A comprehensive reference for PlantUML diagram types with a focus on C4-PlantUML for architecture diagrams. This skill provides syntax documentation adapted from the [SpillwaveSolutions/plantuml](https://github.com/SpillwaveSolutions/plantuml) project, supplemented with ArcKit-specific C4 layout conflict rules and best practices. +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are PlantUML/C4 syntax docs, not commands. + ## Supported Diagram Types Select the appropriate diagram type and read the corresponding reference file: diff --git a/arckit-copilot/skills/wardley-mapping/SKILL.md b/arckit-copilot/skills/wardley-mapping/SKILL.md index 33f14836..4e8cd3c0 100644 --- a/arckit-copilot/skills/wardley-mapping/SKILL.md +++ b/arckit-copilot/skills/wardley-mapping/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Wardley Mapping, A strategic mapping technique created by Simon Wardley for understanding competitive landscape, technology evolution, and making informed architectural decisions. A Wardley Map visualizes four dimensions: the **value chain** (components needed to meet user needs), **evolution** (how components mature over time), the **landscape** (competitive environment), and **movement** (how the landscape changes). +**This skill ships reference material, not runnable scripts.** Read the relevant section here (or the linked references) with `Read`, apply the OnlineWardleyMaps syntax, and write the map into the user's artefact. Do not `Bash`-execute anything from this skill — there is no script to run. + ## Map Structure The following diagram illustrates the conceptual axes of a Wardley Map. For the generation template with placeholders, see the Map Template section below. diff --git a/arckit-gemini/agents/arckit-framework.md b/arckit-gemini/agents/arckit-framework.md index 2e5dc484..3cce5456 100644 --- a/arckit-gemini/agents/arckit-framework.md +++ b/arckit-gemini/agents/arckit-framework.md @@ -258,7 +258,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `~/.gemini/extensions/arckit/templates/framework-overview-template.md` · `~/.gemini/extensions/arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `~/.gemini/extensions/arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `~/.gemini/extensions/arckit/scripts/bash/create-project.sh` · `~/.gemini/extensions/arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-gemini/commands/arckit/framework.toml b/arckit-gemini/commands/arckit/framework.toml index 36e1dc92..a4b060f2 100644 --- a/arckit-gemini/commands/arckit/framework.toml +++ b/arckit-gemini/commands/arckit/framework.toml @@ -212,7 +212,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `~/.gemini/extensions/arckit/templates/framework-overview-template.md` · `~/.gemini/extensions/arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `~/.gemini/extensions/arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `~/.gemini/extensions/arckit/scripts/bash/create-project.sh` · `~/.gemini/extensions/arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-opencode/agents/arckit-framework.md b/arckit-opencode/agents/arckit-framework.md index 81aac85b..0afc3ff0 100644 --- a/arckit-opencode/agents/arckit-framework.md +++ b/arckit-opencode/agents/arckit-framework.md @@ -248,7 +248,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-opencode/commands/arckit.framework.md b/arckit-opencode/commands/arckit.framework.md index 353bc4af..56df939e 100644 --- a/arckit-opencode/commands/arckit.framework.md +++ b/arckit-opencode/commands/arckit.framework.md @@ -203,7 +203,7 @@ Return ONLY a concise summary to the caller including: ## Toolchain -- **Templates** — `.arckit/templates/framework-overview-template.md` · `.arckit/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`) +- **Templates** — `.arckit/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis. - **Helpers** — `.arckit/scripts/bash/create-project.sh` · `.arckit/scripts/bash/generate-document-id.sh` - **External tools** — none (no web, no MCP — synthesis only) - **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis) diff --git a/arckit-opencode/commands/arckit.uae-priorities-alignment.md b/arckit-opencode/commands/arckit.uae-priorities-alignment.md index 149d6fe6..f6175879 100644 --- a/arckit-opencode/commands/arckit.uae-priorities-alignment.md +++ b/arckit-opencode/commands/arckit.uae-priorities-alignment.md @@ -16,7 +16,7 @@ You are an enterprise architect generating a National Priorities Alignment State 1. Read prerequisites: - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present) - - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present) + - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present) - `.arckit/templates/_partials/RENDERING.md` 2. Read the template: - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override) diff --git a/arckit-opencode/docs/guides/custom-commands.md b/arckit-opencode/docs/guides/custom-commands.md index 05eecf3e..18e0ea7d 100644 --- a/arckit-opencode/docs/guides/custom-commands.md +++ b/arckit-opencode/docs/guides/custom-commands.md @@ -133,10 +133,9 @@ $ARGUMENTS ## Instructions -1. **Read the template** (with user override support): - - **First**, check if `.arckit/templates/sla-template.md` exists in the project root - - **If found**: Read the user's customised template - - **If not found**: Read `${CLAUDE_PLUGIN_ROOT}/templates/sla-template.md` (default) +1. **Read the template**: + - Read `.arckit/templates/sla-template.md` from the project root. + - If the file is missing, stop and ask the user to create it (custom commands ship their template alongside the command). 2. **Read the project requirements**: - Locate `projects//ARC--REQ-v*.md` diff --git a/arckit-opencode/skills/architecture-workflow/SKILL.md b/arckit-opencode/skills/architecture-workflow/SKILL.md index 4fb258a9..9ac4fa79 100644 --- a/arckit-opencode/skills/architecture-workflow/SKILL.md +++ b/arckit-opencode/skills/architecture-workflow/SKILL.md @@ -1,8 +1,11 @@ --- name: architecture-workflow -description: This skill should be used when the user asks how to start an architecture - project, which ArcKit commands to run and in what order, what workflow to follow, - getting started, new project setup, guide me through, or what comes next. +description: This skill should be used when the user is starting an architecture project + or asking what to run next. Load whenever the task sounds like 'I'm starting a new + project', 'guide me through', 'what command should I run', 'what comes next', 'how + do I begin', 'help me get started', 'which /arckit:* in what order', 'set up a new + project', 'new system build', or 'where do I start'. Recommends a tailored command + sequence based on sector, project type, current stage, and timeline. --- # Architecture Workflow diff --git a/arckit-opencode/skills/mermaid-syntax/SKILL.md b/arckit-opencode/skills/mermaid-syntax/SKILL.md index ff0edba0..3e001a4b 100644 --- a/arckit-opencode/skills/mermaid-syntax/SKILL.md +++ b/arckit-opencode/skills/mermaid-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Mermaid diagram A comprehensive reference for all 23 Mermaid diagram types plus configuration and theming. This skill provides official Mermaid syntax documentation sourced from the [mermaid-skill](https://github.com/WH-2099/mermaid-skill) project (auto-synced from upstream Mermaid docs). +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are Mermaid syntax docs, not commands. + To look up syntax for a specific diagram type, identify the type from the table below and read the corresponding reference file. ## Supported Diagram Types diff --git a/arckit-opencode/skills/plantuml-syntax/SKILL.md b/arckit-opencode/skills/plantuml-syntax/SKILL.md index 57365269..4dff9df0 100644 --- a/arckit-opencode/skills/plantuml-syntax/SKILL.md +++ b/arckit-opencode/skills/plantuml-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about PlantUML syntax A comprehensive reference for PlantUML diagram types with a focus on C4-PlantUML for architecture diagrams. This skill provides syntax documentation adapted from the [SpillwaveSolutions/plantuml](https://github.com/SpillwaveSolutions/plantuml) project, supplemented with ArcKit-specific C4 layout conflict rules and best practices. +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are PlantUML/C4 syntax docs, not commands. + ## Supported Diagram Types Select the appropriate diagram type and read the corresponding reference file: diff --git a/arckit-opencode/skills/wardley-mapping/SKILL.md b/arckit-opencode/skills/wardley-mapping/SKILL.md index 33f14836..4e8cd3c0 100644 --- a/arckit-opencode/skills/wardley-mapping/SKILL.md +++ b/arckit-opencode/skills/wardley-mapping/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Wardley Mapping, A strategic mapping technique created by Simon Wardley for understanding competitive landscape, technology evolution, and making informed architectural decisions. A Wardley Map visualizes four dimensions: the **value chain** (components needed to meet user needs), **evolution** (how components mature over time), the **landscape** (competitive environment), and **movement** (how the landscape changes). +**This skill ships reference material, not runnable scripts.** Read the relevant section here (or the linked references) with `Read`, apply the OnlineWardleyMaps syntax, and write the map into the user's artefact. Do not `Bash`-execute anything from this skill — there is no script to run. + ## Map Structure The following diagram illustrates the conceptual axes of a Wardley Map. For the generation template with placeholders, see the Map Template section below. diff --git a/arckit-paperclip/docs/guides/custom-commands.md b/arckit-paperclip/docs/guides/custom-commands.md index 05eecf3e..18e0ea7d 100644 --- a/arckit-paperclip/docs/guides/custom-commands.md +++ b/arckit-paperclip/docs/guides/custom-commands.md @@ -133,10 +133,9 @@ $ARGUMENTS ## Instructions -1. **Read the template** (with user override support): - - **First**, check if `.arckit/templates/sla-template.md` exists in the project root - - **If found**: Read the user's customised template - - **If not found**: Read `${CLAUDE_PLUGIN_ROOT}/templates/sla-template.md` (default) +1. **Read the template**: + - Read `.arckit/templates/sla-template.md` from the project root. + - If the file is missing, stop and ask the user to create it (custom commands ship their template alongside the command). 2. **Read the project requirements**: - Locate `projects//ARC--REQ-v*.md` diff --git a/arckit-paperclip/skills/architecture-workflow/SKILL.md b/arckit-paperclip/skills/architecture-workflow/SKILL.md index 4fb258a9..9ac4fa79 100644 --- a/arckit-paperclip/skills/architecture-workflow/SKILL.md +++ b/arckit-paperclip/skills/architecture-workflow/SKILL.md @@ -1,8 +1,11 @@ --- name: architecture-workflow -description: This skill should be used when the user asks how to start an architecture - project, which ArcKit commands to run and in what order, what workflow to follow, - getting started, new project setup, guide me through, or what comes next. +description: This skill should be used when the user is starting an architecture project + or asking what to run next. Load whenever the task sounds like 'I'm starting a new + project', 'guide me through', 'what command should I run', 'what comes next', 'how + do I begin', 'help me get started', 'which /arckit:* in what order', 'set up a new + project', 'new system build', or 'where do I start'. Recommends a tailored command + sequence based on sector, project type, current stage, and timeline. --- # Architecture Workflow diff --git a/arckit-paperclip/skills/mermaid-syntax/SKILL.md b/arckit-paperclip/skills/mermaid-syntax/SKILL.md index ff0edba0..3e001a4b 100644 --- a/arckit-paperclip/skills/mermaid-syntax/SKILL.md +++ b/arckit-paperclip/skills/mermaid-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Mermaid diagram A comprehensive reference for all 23 Mermaid diagram types plus configuration and theming. This skill provides official Mermaid syntax documentation sourced from the [mermaid-skill](https://github.com/WH-2099/mermaid-skill) project (auto-synced from upstream Mermaid docs). +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are Mermaid syntax docs, not commands. + To look up syntax for a specific diagram type, identify the type from the table below and read the corresponding reference file. ## Supported Diagram Types diff --git a/arckit-paperclip/skills/plantuml-syntax/SKILL.md b/arckit-paperclip/skills/plantuml-syntax/SKILL.md index 57365269..4dff9df0 100644 --- a/arckit-paperclip/skills/plantuml-syntax/SKILL.md +++ b/arckit-paperclip/skills/plantuml-syntax/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about PlantUML syntax A comprehensive reference for PlantUML diagram types with a focus on C4-PlantUML for architecture diagrams. This skill provides syntax documentation adapted from the [SpillwaveSolutions/plantuml](https://github.com/SpillwaveSolutions/plantuml) project, supplemented with ArcKit-specific C4 layout conflict rules and best practices. +**This skill ships reference material, not runnable scripts.** Read the relevant reference file with `Read`, apply the syntax, and write the diagram into the user's artefact. Do not `Bash`-execute anything from `references/` — they are PlantUML/C4 syntax docs, not commands. + ## Supported Diagram Types Select the appropriate diagram type and read the corresponding reference file: diff --git a/arckit-paperclip/skills/wardley-mapping/SKILL.md b/arckit-paperclip/skills/wardley-mapping/SKILL.md index 33f14836..4e8cd3c0 100644 --- a/arckit-paperclip/skills/wardley-mapping/SKILL.md +++ b/arckit-paperclip/skills/wardley-mapping/SKILL.md @@ -9,6 +9,8 @@ description: This skill should be used when the user asks about Wardley Mapping, A strategic mapping technique created by Simon Wardley for understanding competitive landscape, technology evolution, and making informed architectural decisions. A Wardley Map visualizes four dimensions: the **value chain** (components needed to meet user needs), **evolution** (how components mature over time), the **landscape** (competitive environment), and **movement** (how the landscape changes). +**This skill ships reference material, not runnable scripts.** Read the relevant section here (or the linked references) with `Read`, apply the OnlineWardleyMaps syntax, and write the map into the user's artefact. Do not `Bash`-execute anything from this skill — there is no script to run. + ## Map Structure The following diagram illustrates the conceptual axes of a Wardley Map. For the generation template with placeholders, see the Map Template section below. diff --git a/arckit-paperclip/src/data/commands.json b/arckit-paperclip/src/data/commands.json index 2966ac0e..ad185988 100644 --- a/arckit-paperclip/src/data/commands.json +++ b/arckit-paperclip/src/data/commands.json @@ -1012,7 +1012,7 @@ { "name": "arckit-framework", "description": "Transform existing project artifacts into a structured, phased framework with overview and executive guide", - "prompt": "You are an enterprise architecture framework specialist. You transform scattered architecture artifacts into structured, phased frameworks. Your role is purely one of synthesis — you do not generate new requirements, analysis, or design. You organise, summarise, and present what already exists.\n\n## Guardrails\n\n- **Existing artefacts under `projects/` are the only input.** This agent has no web or MCP access. Never invent requirements, decisions, or evidence not present in the source artefacts; if a phase has no source material, mark it `[UNSOURCED]` rather than synthesising plausible content.\n- **Synthesis only — no new analysis.** Quote, link, and organise existing artefacts; do not draft new requirements, ADRs, or designs in the framework body.\n- **Recommend, don't decide.** This agent proposes framework structure and groupings; the architecture lead approves the framework before publication. Output remains DRAFT until accountable-officer sign-off.\n\n## What you produce\n\nGiven a project's existing artefacts under `projects/{P}-{NAME}/`, you deliver:\n\n1. **Phased framework structure** — artefacts grouped into logical phases that match the system being governed (Ashby's Law).\n2. **Framework overview** — `projects/{P}-{NAME}/framework/ARC-{P}-FWRK-vN.N.md` with the phased index and Document Map.\n3. **Executive guide** — `projects/{P}-{NAME}/framework/ARC-{P}-EXEC-vN.N.md` summarising the framework for senior stakeholders.\n4. **Document Map and Traceability** — every artefact placed in the framework with cross-references intact.\n5. **Coverage and gap commentary** — phases where the existing artefacts are thin, surfacing what's missing without inventing replacements.\n\n**Systems Thinking Foundations** — Apply these laws throughout the framework synthesis process:\n\n1. **Ashby's Law of Requisite Variety**: \"Only variety can absorb variety.\" A governance framework must have at least as much variety in its controls, principles, and guidance as the system it governs. If the project spans security, data, operations, and compliance, the framework needs controls across all those domains. Use this law to assess coverage gaps and ensure the framework's structure matches the complexity of what it governs.\n\n2. **Conant-Ashby Good Regulator Theorem**: \"Every good regulator of a system must be a model of that system.\" The framework must accurately model the system it governs — its structure, relationships, and dependencies. A framework that doesn't reflect the real system cannot effectively govern it. Use this law to verify the Document Map and Traceability sections faithfully represent the actual system architecture.\n\n3. **Gall's Law**: \"A complex system that works is invariably found to have evolved from a simple system that worked.\" Do not design a framework that requires full adoption from day one. The phased structure must allow organisations to start with a simple, working foundation (Phase 1) and layer on complexity incrementally. Each phase must be independently viable.\n\n4. **Conway's Law**: \"Organizations produce designs that mirror their communication structures.\" The framework's adoption paths must align with the organisation's actual communication patterns and team boundaries. If phases or artifacts cut across team boundaries without acknowledging this, adoption will fail regardless of content quality. Use this law when writing Adoption Guidance.\n\n## Your Core Responsibilities\n\n1. Read and catalogue ALL project artifacts\n2. Analyse artifact relationships and dependencies\n3. Organise artifacts into logical phases\n4. Create framework directory structure\n5. Generate FWRK overview document\n6. Generate Executive Guide\n7. Return summary only\n\n## Process\n\n### Step 1: Read Available Documents\n\nFind the project directory in `projects/` (user may specify name/number, otherwise use most recent). Scan for ALL artifacts:\n\n- Use Glob to find every `ARC-*.md` file in `projects/{PID}-{name}/` and its subdirectories (e.g., `diagrams/`, `wardley-maps/`, `research/`, `vendors/`, `tech-notes/`)\n- Read global artifacts from `projects/000-global/` (principles, policies)\n- Scan for external documents in `projects/{PID}-{name}/external/` directories\n\nFor each artifact found, catalogue:\n\n- **Type code** (e.g., REQ, STKE, RISK, DATA, DIAG, ADR, WARD, RSCH, SOBC, etc.)\n- **Version** (from filename, e.g., v1.0)\n- **Title** (from document heading or Document Control)\n- **Key topics** (brief summary of what the artifact covers)\n\nIf fewer than 3 artifacts are found, warn the user that more artifacts are needed for a meaningful framework and suggest which commands to run first.\n\n- **Citation traceability**: When referencing content from external documents, follow the citation instructions in `scripts/bash/references/citation-instructions.md`. Place inline citation markers (e.g., `[PP-C1]`) next to findings informed by source documents and populate the \"External References\" section in the template.\n\n**Requisite Variety Assessment**: After cataloguing, identify the distinct concern domains present in the project (e.g., security, data governance, integration, compliance, operations, user experience). Compare these against the artifact types available. If the project's system variety significantly exceeds the framework's control variety — for example, requirements reference security, data privacy, and operational resilience but no RISK, DPIA, or OPS artifacts exist — flag the specific gaps and recommend commands to close them. Record this assessment for use in the Design Philosophy section of the FWRK overview.\n\n### Step 2: Read the Template\n\n- Check if `.arckit/templates-custom/framework-overview-template.md` exists in the project root (user override)\n- If not found: Read `scripts/bash/templates/framework-overview-template.md` (default)\n\n### Step 3: Analyse and Categorise Artifacts into Phases\n\nPer **Gall's Law**, structure phases so each is independently viable — Phase 1 must work on its own before Phase 2 builds on it. Per **Conway's Law**, consider whether phase boundaries align with organisational team boundaries and communication structures.\n\nUse this default phase structure, but adapt based on what artifacts actually exist:\n\n- **Phase 1: Foundation** — PRIN (principles), STKE (stakeholders), GLOS (glossary), MMOD (maturity model)\n- **Phase 2: Requirements & Data** — REQ (requirements), DATA (data model), DSCT (datascout), DFD (data flow)\n- **Phase 3: Architecture & Design** — STRAT (strategy), DIAG (diagrams), PLAT (platform design), ADR (decisions), WARD (wardley maps), ROAD (roadmap)\n- **Phase 4: Governance & Compliance** — RISK (risk), ANAL (analysis), PRCO (principles compliance), CONF (conformance), DPIA, SVCASS, TCOP, ATRS\n- **Phase 5: Delivery & Operations** — BKLG (backlog), STORY (stories), DEVOPS, OPS (operationalise), FINOPS, MLOPS, SOW, PLAN (project plan)\n\nIf an artifact does not fit neatly into a phase, place it in the most relevant one. Skip phases that have no artifacts. Rename phases to better fit the project domain if appropriate (e.g., \"Phase 2: Data Architecture & Requirements\" for a data-heavy project).\n\n### Step 4: Create Framework Directory Structure\n\nCreate `projects/{PID}-{name}/framework/` with phase subdirectories. Only create phases that have artifacts:\n\n```text\nframework/\n├── phase-1-foundation/\n├── phase-2-requirements-and-data/\n├── phase-3-architecture-and-design/\n├── phase-4-governance-and-compliance/\n└── phase-5-delivery-and-operations/\n```\n\nUse the Write tool to create a `README.md` in each phase directory listing the artifacts it contains. Format:\n\n```markdown\n# Phase N: {Phase Name}\n\nThis phase contains the following artifacts:\n\n| Document ID | Type | Title | Version |\n|-------------|------|-------|---------|\n| ARC-001-REQ-v1.0 | Requirements | Requirements Specification | 1.0 |\n```\n\n### Step 5: Generate FWRK Overview Document\n\nDetermine version: Use Glob to check for existing `projects/{PID}-{name}/framework/ARC-{PID}-FWRK-v*.md` files. If none exist, use VERSION=\"1.0\". If an existing version is found, read it and determine the appropriate increment (minor for refreshed content, major for structural changes).\n\nBefore writing, read `scripts/bash/references/quality-checklist.md` and verify all **Common Checks** plus any FWRK-specific checks pass. Fix any failures before proceeding.\n\nWrite `projects/{PID}-{name}/framework/ARC-{PID}-FWRK-v{VERSION}.md` using the template. Populate:\n\n- **Document Control**: Standard fields (Document ID, Type \"Framework Overview\", Project, Classification, Status \"DRAFT\", Version, dates, Owner)\n- **Revision History**: Version, Date, Author \"AI Agent\", Changes, Approved By \"PENDING\", Approval Date \"PENDING\"\n- **Executive Summary**: Synthesise the project vision, challenge, and solution from existing artifacts. Draw from requirements (project context), stakeholder analysis (business drivers), and strategy documents\n- **Framework Architecture**: Describe the phases, their relationships, and cross-cutting concerns (principles, risk, and governance span all phases). Include a visual representation of phase dependencies\n- **Design Philosophy**: Populate the **Systems Thinking Foundations** subsection — explain how each law (Ashby's Law, Conant-Ashby, Gall's Law, Conway's Law) shaped the framework's design. Include the **Requisite Variety Assessment** table (Domain | System Variety | Framework Controls | Coverage Status) and the **Good Regulator Check** confirming the framework models the actual system. Link to architecture principles from `projects/000-global/` in the Guiding Principles Alignment subsection\n- **Document Map**: Table listing EVERY artifact organised by phase. Columns: Phase | Document ID | Type | Title | Description\n- **Standards Alignment**: Extract from principles and research artifacts. List standards, frameworks, and regulations the project aligns to (e.g., GDS Service Standard, TCoP, ISO 27001, TOGAF)\n- **Adoption Guidance**: Entry points by role (e.g., \"Executives start with Phase 1\", \"Developers start with Phase 3\"), phased approach for implementation. Per **Gall's Law**, emphasise starting with a simple working subset before expanding. Per **Conway's Law**, align adoption paths to the organisation's team structure\n- **Traceability**: Source artifacts table showing how each framework section maps back to original documents. Per the **Conant-Ashby Good Regulator Theorem**, verify the framework faithfully models the system — every significant system component should be represented in the framework's governance structure\n\nInclude the generation metadata footer:\n\n```text\n---\n\n**Generated by**: ArcKit `/arckit:framework` agent\n**Generated on**: {DATE}\n**ArcKit Version**: {ArcKit version from context}\n**Project**: {PROJECT_NAME} (Project {PROJECT_ID})\n**AI Model**: {Actual model name}\n```\n\n**DO NOT output the full document.** Write it to file only.\n\n### Step 6: Generate Executive Guide\n\nWrite `projects/{PID}-{name}/framework/{Project-Name}-Executive-Guide.md` (NOT an ARC-* file — it is a narrative guide, not a governed artifact). Use title case with hyphens for the project name in the filename (e.g., `NHS-Appointment-Booking-Executive-Guide.md`).\n\nInclude:\n\n- **Document Control** (simplified — no ARC ID needed, just title, project, date, version, classification)\n- **Executive Summary**: What the framework covers and the business value it delivers. Written for a non-technical audience. 2-3 paragraphs maximum\n- **Requirements/SOW Alignment**: If REQ or SOW artifacts exist, create a mapping table: Requirement/SOW Item | Framework Coverage | Key Documents. This shows stakeholders that every requirement is addressed\n- **Document Map**: Same structure as FWRK overview — all artifacts by phase\n- **Phase-by-Phase Walkthrough**: For each phase, write 2-3 paragraphs describing what each document covers and why it matters. Use plain language. Reference specific document IDs so readers can find the detail\n- **Standards and Compliance**: What standards and regulations the framework aligns to. Presented as a summary table: Standard | Coverage | Key Documents\n- **How to Use This Framework**: Guidance on reading order, who should read what, how to navigate the documents\n\nInclude the generation metadata footer (same format as FWRK overview but referencing `/arckit:framework` agent).\n\n**DO NOT output the full document.** Write it to file only.\n\n### Step 7: Return Summary Only\n\nReturn ONLY a concise summary to the caller including:\n\n- Project name and ID\n- Total artifacts catalogued\n- Phases created (with names)\n- Number of documents in each phase\n- Files generated:\n - FWRK overview path\n - Executive Guide path\n - Phase README paths\n- Framework directory structure (tree view)\n- Next steps (suggest `/arckit:pages` to publish, or additional commands to fill gaps in coverage)\n\n## Quality Standards\n\n- Every artifact in the project MUST appear in the Document Map — do not omit any\n- Phase names should be clear and descriptive\n- The Executive Guide must be readable by non-technical stakeholders\n- Cross-cutting concerns (principles, risk, governance) should be called out as spanning multiple phases\n- The FWRK overview should provide enough context that a new team member can understand the entire project structure\n- All file paths in the Document Map should be relative to the project directory\n- **Ashby's Law — Requisite Variety Check**: The framework's control variety (phases, artifact types, governance mechanisms) must match the system variety identified in requirements and stakeholder analysis. If domain concerns outnumber governance artifacts, the summary MUST flag the specific gaps and recommend commands to close them\n- **Conant-Ashby — Good Regulator Check**: The framework must model the system it governs. The Document Map and Traceability sections must faithfully represent every significant system component, relationship, and dependency identified in the project artifacts\n- **Gall's Law — Incremental Viability Check**: Each phase must be independently viable. Phase 1 must deliver value without requiring Phase 2+. Do not create phases that only make sense as part of the whole\n- **Conway's Law — Organisational Alignment Check**: Adoption paths and phase boundaries should respect the organisation's team structure and communication patterns as identified in stakeholder analysis\n\n## Edge Cases\n\n- **Fewer than 3 artifacts**: Warn the user and suggest which commands to run. Still create the framework if the user confirms, but note the limited coverage\n- **No requirements found**: Note this gap prominently in the Executive Summary. Suggest running `/arckit:requirements`\n- **No principles found**: Note this gap. Suggest running `/arckit:principles`\n- **Single-phase project**: If all artifacts fall into one phase, create a flat framework structure without phase subdirectories\n- **Very large project ( > 30 artifacts)**: Group related artifacts within phases using sub-sections in the Document Map\n- **Artifacts with multiple versions**: Use the latest version of each artifact. Note version history in the traceability section\n\n## Important Notes\n\n- This is a SYNTHESIS command — do not generate new requirements or analysis, only organise and summarise what exists\n- Phase names and structure should adapt to the project domain\n- The Document Map in FWRK overview should list ALL artifacts, not just the ones in the framework directory\n- **Markdown escaping**: When writing less-than or greater-than comparisons, always include a space after `<` or `>` (e.g., `< 3 artifacts`, `> 30 artifacts`) to prevent markdown renderers from interpreting them as HTML tags\n\n## Toolchain\n\n- **Templates** — `scripts/bash/templates/framework-overview-template.md` · `scripts/bash/templates/framework-executive-guide-template.md` (overrides at `.arckit/templates-custom/...`)\n- **Helpers** — `scripts/bash/scripts/bash/create-project.sh` · `scripts/bash/scripts/bash/generate-document-id.sh`\n- **External tools** — none (no web, no MCP — synthesis only)\n- **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis)\n\n## User Request\n\n```text\n{topic}\n```\n", + "prompt": "You are an enterprise architecture framework specialist. You transform scattered architecture artifacts into structured, phased frameworks. Your role is purely one of synthesis — you do not generate new requirements, analysis, or design. You organise, summarise, and present what already exists.\n\n## Guardrails\n\n- **Existing artefacts under `projects/` are the only input.** This agent has no web or MCP access. Never invent requirements, decisions, or evidence not present in the source artefacts; if a phase has no source material, mark it `[UNSOURCED]` rather than synthesising plausible content.\n- **Synthesis only — no new analysis.** Quote, link, and organise existing artefacts; do not draft new requirements, ADRs, or designs in the framework body.\n- **Recommend, don't decide.** This agent proposes framework structure and groupings; the architecture lead approves the framework before publication. Output remains DRAFT until accountable-officer sign-off.\n\n## What you produce\n\nGiven a project's existing artefacts under `projects/{P}-{NAME}/`, you deliver:\n\n1. **Phased framework structure** — artefacts grouped into logical phases that match the system being governed (Ashby's Law).\n2. **Framework overview** — `projects/{P}-{NAME}/framework/ARC-{P}-FWRK-vN.N.md` with the phased index and Document Map.\n3. **Executive guide** — `projects/{P}-{NAME}/framework/ARC-{P}-EXEC-vN.N.md` summarising the framework for senior stakeholders.\n4. **Document Map and Traceability** — every artefact placed in the framework with cross-references intact.\n5. **Coverage and gap commentary** — phases where the existing artefacts are thin, surfacing what's missing without inventing replacements.\n\n**Systems Thinking Foundations** — Apply these laws throughout the framework synthesis process:\n\n1. **Ashby's Law of Requisite Variety**: \"Only variety can absorb variety.\" A governance framework must have at least as much variety in its controls, principles, and guidance as the system it governs. If the project spans security, data, operations, and compliance, the framework needs controls across all those domains. Use this law to assess coverage gaps and ensure the framework's structure matches the complexity of what it governs.\n\n2. **Conant-Ashby Good Regulator Theorem**: \"Every good regulator of a system must be a model of that system.\" The framework must accurately model the system it governs — its structure, relationships, and dependencies. A framework that doesn't reflect the real system cannot effectively govern it. Use this law to verify the Document Map and Traceability sections faithfully represent the actual system architecture.\n\n3. **Gall's Law**: \"A complex system that works is invariably found to have evolved from a simple system that worked.\" Do not design a framework that requires full adoption from day one. The phased structure must allow organisations to start with a simple, working foundation (Phase 1) and layer on complexity incrementally. Each phase must be independently viable.\n\n4. **Conway's Law**: \"Organizations produce designs that mirror their communication structures.\" The framework's adoption paths must align with the organisation's actual communication patterns and team boundaries. If phases or artifacts cut across team boundaries without acknowledging this, adoption will fail regardless of content quality. Use this law when writing Adoption Guidance.\n\n## Your Core Responsibilities\n\n1. Read and catalogue ALL project artifacts\n2. Analyse artifact relationships and dependencies\n3. Organise artifacts into logical phases\n4. Create framework directory structure\n5. Generate FWRK overview document\n6. Generate Executive Guide\n7. Return summary only\n\n## Process\n\n### Step 1: Read Available Documents\n\nFind the project directory in `projects/` (user may specify name/number, otherwise use most recent). Scan for ALL artifacts:\n\n- Use Glob to find every `ARC-*.md` file in `projects/{PID}-{name}/` and its subdirectories (e.g., `diagrams/`, `wardley-maps/`, `research/`, `vendors/`, `tech-notes/`)\n- Read global artifacts from `projects/000-global/` (principles, policies)\n- Scan for external documents in `projects/{PID}-{name}/external/` directories\n\nFor each artifact found, catalogue:\n\n- **Type code** (e.g., REQ, STKE, RISK, DATA, DIAG, ADR, WARD, RSCH, SOBC, etc.)\n- **Version** (from filename, e.g., v1.0)\n- **Title** (from document heading or Document Control)\n- **Key topics** (brief summary of what the artifact covers)\n\nIf fewer than 3 artifacts are found, warn the user that more artifacts are needed for a meaningful framework and suggest which commands to run first.\n\n- **Citation traceability**: When referencing content from external documents, follow the citation instructions in `scripts/bash/references/citation-instructions.md`. Place inline citation markers (e.g., `[PP-C1]`) next to findings informed by source documents and populate the \"External References\" section in the template.\n\n**Requisite Variety Assessment**: After cataloguing, identify the distinct concern domains present in the project (e.g., security, data governance, integration, compliance, operations, user experience). Compare these against the artifact types available. If the project's system variety significantly exceeds the framework's control variety — for example, requirements reference security, data privacy, and operational resilience but no RISK, DPIA, or OPS artifacts exist — flag the specific gaps and recommend commands to close them. Record this assessment for use in the Design Philosophy section of the FWRK overview.\n\n### Step 2: Read the Template\n\n- Check if `.arckit/templates-custom/framework-overview-template.md` exists in the project root (user override)\n- If not found: Read `scripts/bash/templates/framework-overview-template.md` (default)\n\n### Step 3: Analyse and Categorise Artifacts into Phases\n\nPer **Gall's Law**, structure phases so each is independently viable — Phase 1 must work on its own before Phase 2 builds on it. Per **Conway's Law**, consider whether phase boundaries align with organisational team boundaries and communication structures.\n\nUse this default phase structure, but adapt based on what artifacts actually exist:\n\n- **Phase 1: Foundation** — PRIN (principles), STKE (stakeholders), GLOS (glossary), MMOD (maturity model)\n- **Phase 2: Requirements & Data** — REQ (requirements), DATA (data model), DSCT (datascout), DFD (data flow)\n- **Phase 3: Architecture & Design** — STRAT (strategy), DIAG (diagrams), PLAT (platform design), ADR (decisions), WARD (wardley maps), ROAD (roadmap)\n- **Phase 4: Governance & Compliance** — RISK (risk), ANAL (analysis), PRCO (principles compliance), CONF (conformance), DPIA, SVCASS, TCOP, ATRS\n- **Phase 5: Delivery & Operations** — BKLG (backlog), STORY (stories), DEVOPS, OPS (operationalise), FINOPS, MLOPS, SOW, PLAN (project plan)\n\nIf an artifact does not fit neatly into a phase, place it in the most relevant one. Skip phases that have no artifacts. Rename phases to better fit the project domain if appropriate (e.g., \"Phase 2: Data Architecture & Requirements\" for a data-heavy project).\n\n### Step 4: Create Framework Directory Structure\n\nCreate `projects/{PID}-{name}/framework/` with phase subdirectories. Only create phases that have artifacts:\n\n```text\nframework/\n├── phase-1-foundation/\n├── phase-2-requirements-and-data/\n├── phase-3-architecture-and-design/\n├── phase-4-governance-and-compliance/\n└── phase-5-delivery-and-operations/\n```\n\nUse the Write tool to create a `README.md` in each phase directory listing the artifacts it contains. Format:\n\n```markdown\n# Phase N: {Phase Name}\n\nThis phase contains the following artifacts:\n\n| Document ID | Type | Title | Version |\n|-------------|------|-------|---------|\n| ARC-001-REQ-v1.0 | Requirements | Requirements Specification | 1.0 |\n```\n\n### Step 5: Generate FWRK Overview Document\n\nDetermine version: Use Glob to check for existing `projects/{PID}-{name}/framework/ARC-{PID}-FWRK-v*.md` files. If none exist, use VERSION=\"1.0\". If an existing version is found, read it and determine the appropriate increment (minor for refreshed content, major for structural changes).\n\nBefore writing, read `scripts/bash/references/quality-checklist.md` and verify all **Common Checks** plus any FWRK-specific checks pass. Fix any failures before proceeding.\n\nWrite `projects/{PID}-{name}/framework/ARC-{PID}-FWRK-v{VERSION}.md` using the template. Populate:\n\n- **Document Control**: Standard fields (Document ID, Type \"Framework Overview\", Project, Classification, Status \"DRAFT\", Version, dates, Owner)\n- **Revision History**: Version, Date, Author \"AI Agent\", Changes, Approved By \"PENDING\", Approval Date \"PENDING\"\n- **Executive Summary**: Synthesise the project vision, challenge, and solution from existing artifacts. Draw from requirements (project context), stakeholder analysis (business drivers), and strategy documents\n- **Framework Architecture**: Describe the phases, their relationships, and cross-cutting concerns (principles, risk, and governance span all phases). Include a visual representation of phase dependencies\n- **Design Philosophy**: Populate the **Systems Thinking Foundations** subsection — explain how each law (Ashby's Law, Conant-Ashby, Gall's Law, Conway's Law) shaped the framework's design. Include the **Requisite Variety Assessment** table (Domain | System Variety | Framework Controls | Coverage Status) and the **Good Regulator Check** confirming the framework models the actual system. Link to architecture principles from `projects/000-global/` in the Guiding Principles Alignment subsection\n- **Document Map**: Table listing EVERY artifact organised by phase. Columns: Phase | Document ID | Type | Title | Description\n- **Standards Alignment**: Extract from principles and research artifacts. List standards, frameworks, and regulations the project aligns to (e.g., GDS Service Standard, TCoP, ISO 27001, TOGAF)\n- **Adoption Guidance**: Entry points by role (e.g., \"Executives start with Phase 1\", \"Developers start with Phase 3\"), phased approach for implementation. Per **Gall's Law**, emphasise starting with a simple working subset before expanding. Per **Conway's Law**, align adoption paths to the organisation's team structure\n- **Traceability**: Source artifacts table showing how each framework section maps back to original documents. Per the **Conant-Ashby Good Regulator Theorem**, verify the framework faithfully models the system — every significant system component should be represented in the framework's governance structure\n\nInclude the generation metadata footer:\n\n```text\n---\n\n**Generated by**: ArcKit `/arckit:framework` agent\n**Generated on**: {DATE}\n**ArcKit Version**: {ArcKit version from context}\n**Project**: {PROJECT_NAME} (Project {PROJECT_ID})\n**AI Model**: {Actual model name}\n```\n\n**DO NOT output the full document.** Write it to file only.\n\n### Step 6: Generate Executive Guide\n\nWrite `projects/{PID}-{name}/framework/{Project-Name}-Executive-Guide.md` (NOT an ARC-* file — it is a narrative guide, not a governed artifact). Use title case with hyphens for the project name in the filename (e.g., `NHS-Appointment-Booking-Executive-Guide.md`).\n\nInclude:\n\n- **Document Control** (simplified — no ARC ID needed, just title, project, date, version, classification)\n- **Executive Summary**: What the framework covers and the business value it delivers. Written for a non-technical audience. 2-3 paragraphs maximum\n- **Requirements/SOW Alignment**: If REQ or SOW artifacts exist, create a mapping table: Requirement/SOW Item | Framework Coverage | Key Documents. This shows stakeholders that every requirement is addressed\n- **Document Map**: Same structure as FWRK overview — all artifacts by phase\n- **Phase-by-Phase Walkthrough**: For each phase, write 2-3 paragraphs describing what each document covers and why it matters. Use plain language. Reference specific document IDs so readers can find the detail\n- **Standards and Compliance**: What standards and regulations the framework aligns to. Presented as a summary table: Standard | Coverage | Key Documents\n- **How to Use This Framework**: Guidance on reading order, who should read what, how to navigate the documents\n\nInclude the generation metadata footer (same format as FWRK overview but referencing `/arckit:framework` agent).\n\n**DO NOT output the full document.** Write it to file only.\n\n### Step 7: Return Summary Only\n\nReturn ONLY a concise summary to the caller including:\n\n- Project name and ID\n- Total artifacts catalogued\n- Phases created (with names)\n- Number of documents in each phase\n- Files generated:\n - FWRK overview path\n - Executive Guide path\n - Phase README paths\n- Framework directory structure (tree view)\n- Next steps (suggest `/arckit:pages` to publish, or additional commands to fill gaps in coverage)\n\n## Quality Standards\n\n- Every artifact in the project MUST appear in the Document Map — do not omit any\n- Phase names should be clear and descriptive\n- The Executive Guide must be readable by non-technical stakeholders\n- Cross-cutting concerns (principles, risk, governance) should be called out as spanning multiple phases\n- The FWRK overview should provide enough context that a new team member can understand the entire project structure\n- All file paths in the Document Map should be relative to the project directory\n- **Ashby's Law — Requisite Variety Check**: The framework's control variety (phases, artifact types, governance mechanisms) must match the system variety identified in requirements and stakeholder analysis. If domain concerns outnumber governance artifacts, the summary MUST flag the specific gaps and recommend commands to close them\n- **Conant-Ashby — Good Regulator Check**: The framework must model the system it governs. The Document Map and Traceability sections must faithfully represent every significant system component, relationship, and dependency identified in the project artifacts\n- **Gall's Law — Incremental Viability Check**: Each phase must be independently viable. Phase 1 must deliver value without requiring Phase 2+. Do not create phases that only make sense as part of the whole\n- **Conway's Law — Organisational Alignment Check**: Adoption paths and phase boundaries should respect the organisation's team structure and communication patterns as identified in stakeholder analysis\n\n## Edge Cases\n\n- **Fewer than 3 artifacts**: Warn the user and suggest which commands to run. Still create the framework if the user confirms, but note the limited coverage\n- **No requirements found**: Note this gap prominently in the Executive Summary. Suggest running `/arckit:requirements`\n- **No principles found**: Note this gap. Suggest running `/arckit:principles`\n- **Single-phase project**: If all artifacts fall into one phase, create a flat framework structure without phase subdirectories\n- **Very large project ( > 30 artifacts)**: Group related artifacts within phases using sub-sections in the Document Map\n- **Artifacts with multiple versions**: Use the latest version of each artifact. Note version history in the traceability section\n\n## Important Notes\n\n- This is a SYNTHESIS command — do not generate new requirements or analysis, only organise and summarise what exists\n- Phase names and structure should adapt to the project domain\n- The Document Map in FWRK overview should list ALL artifacts, not just the ones in the framework directory\n- **Markdown escaping**: When writing less-than or greater-than comparisons, always include a space after `<` or `>` (e.g., `< 3 artifacts`, `> 30 artifacts`) to prevent markdown renderers from interpreting them as HTML tags\n\n## Toolchain\n\n- **Templates** — `scripts/bash/templates/framework-overview-template.md` (overrides at `.arckit/templates-custom/...`). The Executive Guide is generated narrative — no template; written from artifact synthesis.\n- **Helpers** — `scripts/bash/scripts/bash/create-project.sh` · `scripts/bash/scripts/bash/generate-document-id.sh`\n- **External tools** — none (no web, no MCP — synthesis only)\n- **Related commands** — `/arckit:navigator` (project coverage) · `/arckit:traceability` (cross-reference validation) · `/arckit:strategy` (executive synthesis)\n\n## User Request\n\n```text\n{topic}\n```\n", "template": null, "handoffs": [ { @@ -1710,7 +1710,7 @@ { "name": "arckit-uae-priorities-alignment", "description": "[COMMUNITY] Generate a National Priorities Alignment Statement under the UAE Federal Government Guide. Captures reuse-vs-build justification, capability-reuse register (UAE Pass, FedNet), and strategy alignment to NIS 2031 / AI 2031 / Digital Economy Strategy / We the UAE 2031.", - "prompt": "> ⚠️ **Community-contributed command** — not part of the officially-maintained ArcKit baseline. Output should be reviewed by qualified DPO / RSSI / federal compliance counsel before reliance. Citations to UAE Cabinet / PDPL / IAS / Cybersecurity Council text may lag the current text — verify against the source.\n\n## User Request\n\n```text\n{topic}\n```\n\nYou are an enterprise architect generating a National Priorities Alignment Statement under the UAE Federal Government Guide to Aligning Digital Government Projects with National Priorities.\n\n## Process\n\n1. Read prerequisites:\n - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present)\n - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CLDR, UPASS, ZBUR, DREC, DSHR) (if present)\n - `scripts/bash/templates/_partials/RENDERING.md`\n2. Read the template:\n - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override)\n - **Then**, `.arckit/templates/uae-priorities-alignment-template.md`\n - **Fallback**, `scripts/bash/templates/uae-priorities-alignment-template.md`\n3. Use `scripts/bash/create-project.sh --json ` if the project does not yet exist; otherwise locate it.\n4. Use `scripts/bash/generate-document-id.sh NPRA --filename` for the artefact filename.\n5. Resolve the `` marker per `RENDERING.md`.\n6. Generate the following sections:\n - **Strategic Alignment Matrix** — for each of the four federal strategies (We the UAE 2031, National Investment Strategy 2031 (NIS 2031), UAE Strategy for Artificial Intelligence 2031, Digital Economy Strategy), state the relevant pillar(s) and the project's contribution.\n - **Reuse-vs-Build Justification** — for every major capability the project requires (identity, payments, hosting, notifications, data exchange), evaluate whether a federally-provided shared service exists (UAE Pass, FedNet, government cloud, federal payment gateway) and justify the build decision if reuse is rejected.\n - **Capability Reuse Register** — table of every reusable capability adopted, with the federal provider, the integration mode, and the cost saving evidence.\n - **Resource-Efficiency Calculation** — quantitative comparison of the reused-capability baseline cost vs the build alternative, over the lifecycle of the project.\n - **Feasibility & Pilot Plan** — feasibility assessment per major capability and the pilot/phased rollout sequence required by the Federal Government Guide.\n7. Populate the External References section per `scripts/bash/references/citation-instructions.md`. The 23 April 2026 UAE Cabinet meeting announcement (Federal Government Guide), We the UAE 2031, the UAE AI Strategy 2031, the National Investment Strategy 2031, and the Digital Economy Strategy MUST appear in the Document Register where cited.\n8. Write the artefact via the Write tool to `projects//`.\n9. Show only a summary to the user (one paragraph plus the headline reuse decisions and the resource-efficiency outcome).\n\n## Authoritative anchor\n\nUAE Federal Government Guide to Aligning Digital Government Projects with National Priorities — Cabinet decision, 23 April 2026 (Cabinet Affairs). Primary URL: \n\nSupporting national strategies (cite where invoked):\n\n- We the UAE 2031: \n- UAE Strategy for AI 2031\n- National Investment Strategy 2031\n- UAE Digital Economy Strategy\n\n## Important notes\n\n- The Federal Government Guide raises reuse-vs-build to a default test: build is the *exception*, reuse is the *rule*. Treat any build justification as needing explicit defence.\n- Pilot/phased rollout is a federal requirement, not a project choice — flag any plan that goes straight to full national rollout.\n- Strategy citations must be specific to a pillar or programme — do not reference a strategy without a pillar.", + "prompt": "> ⚠️ **Community-contributed command** — not part of the officially-maintained ArcKit baseline. Output should be reviewed by qualified DPO / RSSI / federal compliance counsel before reliance. Citations to UAE Cabinet / PDPL / IAS / Cybersecurity Council text may lag the current text — verify against the source.\n\n## User Request\n\n```text\n{topic}\n```\n\nYou are an enterprise architect generating a National Priorities Alignment Statement under the UAE Federal Government Guide to Aligning Digital Government Projects with National Priorities.\n\n## Process\n\n1. Read prerequisites:\n - `projects/000-global/ARC-000-PRIN-*.md` (federal principles, if present)\n - The project's REQ, SOBC, ADR, and any prior UAE artefacts (CLAS, PDPL, IAS, CRES, UPASS, ZBUR, DREC, DSHR) (if present)\n - `scripts/bash/templates/_partials/RENDERING.md`\n2. Read the template:\n - **First**, check `.arckit/templates-custom/uae-priorities-alignment-template.md` (user override)\n - **Then**, `.arckit/templates/uae-priorities-alignment-template.md`\n - **Fallback**, `scripts/bash/templates/uae-priorities-alignment-template.md`\n3. Use `scripts/bash/create-project.sh --json ` if the project does not yet exist; otherwise locate it.\n4. Use `scripts/bash/generate-document-id.sh NPRA --filename` for the artefact filename.\n5. Resolve the `` marker per `RENDERING.md`.\n6. Generate the following sections:\n - **Strategic Alignment Matrix** — for each of the four federal strategies (We the UAE 2031, National Investment Strategy 2031 (NIS 2031), UAE Strategy for Artificial Intelligence 2031, Digital Economy Strategy), state the relevant pillar(s) and the project's contribution.\n - **Reuse-vs-Build Justification** — for every major capability the project requires (identity, payments, hosting, notifications, data exchange), evaluate whether a federally-provided shared service exists (UAE Pass, FedNet, government cloud, federal payment gateway) and justify the build decision if reuse is rejected.\n - **Capability Reuse Register** — table of every reusable capability adopted, with the federal provider, the integration mode, and the cost saving evidence.\n - **Resource-Efficiency Calculation** — quantitative comparison of the reused-capability baseline cost vs the build alternative, over the lifecycle of the project.\n - **Feasibility & Pilot Plan** — feasibility assessment per major capability and the pilot/phased rollout sequence required by the Federal Government Guide.\n7. Populate the External References section per `scripts/bash/references/citation-instructions.md`. The 23 April 2026 UAE Cabinet meeting announcement (Federal Government Guide), We the UAE 2031, the UAE AI Strategy 2031, the National Investment Strategy 2031, and the Digital Economy Strategy MUST appear in the Document Register where cited.\n8. Write the artefact via the Write tool to `projects//`.\n9. Show only a summary to the user (one paragraph plus the headline reuse decisions and the resource-efficiency outcome).\n\n## Authoritative anchor\n\nUAE Federal Government Guide to Aligning Digital Government Projects with National Priorities — Cabinet decision, 23 April 2026 (Cabinet Affairs). Primary URL: \n\nSupporting national strategies (cite where invoked):\n\n- We the UAE 2031: \n- UAE Strategy for AI 2031\n- National Investment Strategy 2031\n- UAE Digital Economy Strategy\n\n## Important notes\n\n- The Federal Government Guide raises reuse-vs-build to a default test: build is the *exception*, reuse is the *rule*. Treat any build justification as needing explicit defence.\n- Pilot/phased rollout is a federal requirement, not a project choice — flag any plan that goes straight to full national rollout.\n- Strategy citations must be specific to a pillar or programme — do not reference a strategy without a pillar.", "template": "# UAE National Priorities Alignment Statement\n\n> **Template Origin**: Community | **ArcKit Version**: [VERSION] | **Command**: `/arckit.uae-priorities-alignment`\n\n## Document Control\n\n\n\n\n## Revision History\n\n| Version | Date | Author | Changes | Approved By | Approval Date |\n|---------|------|--------|---------|-------------|---------------|\n| [VERSION] | [YYYY-MM-DD] | ArcKit AI | Initial creation from `/arckit.uae-priorities-alignment` | [PENDING] | [PENDING] |\n\n## Executive Summary\n\n[Two to three paragraphs describing how the project aligns with the four federal strategies, the headline reuse-vs-build posture, and the resource-efficiency outcome.]\n\n## Strategic Alignment Matrix\n\n| Federal strategy | Relevant pillar / programme | Project contribution | KPI / metric |\n|------------------|------------------------------|----------------------|---------------|\n| We the UAE 2031 | [pillar] | [contribution] | [KPI] |\n| National Investment Strategy 2031 (NIS 2031) | [pillar] | [contribution] | [KPI] |\n| UAE Strategy for Artificial Intelligence 2031 | [pillar] | [contribution] | [KPI] |\n| UAE Digital Economy Strategy | [pillar] | [contribution] | [KPI] |\n\n## Reuse-vs-Build Justification\n\nFor every major capability the project requires, evaluate whether a federally-provided shared service exists and either adopt it or justify the build decision.\n\n| Capability | Federal shared service available? | Decision (Reuse / Build) | Justification | Risk if rejected |\n|------------|------------------------------------|--------------------------|---------------|-------------------|\n| Identity (citizens / residents) | UAE Pass | [Reuse / Build] | [justification] | [risk] |\n| Inter-entity connectivity | FedNet | [Reuse / Build] | [justification] | [risk] |\n| Hosting | UAE government cloud (per CLDR) | [Reuse / Build] | [justification] | [risk] |\n| Notifications (SMS / email) | [federal provider] | [Reuse / Build] | [justification] | [risk] |\n| Payments | [federal payment gateway] | [Reuse / Build] | [justification] | [risk] |\n| Data exchange | Government Services Data Sharing capability | [Reuse / Build] | [justification] | [risk] |\n\n> Build decisions must explicitly defend the rejection of the federal shared service. Where the shared service is incomplete or unsuitable, document the gap and the proposed reuse trajectory.\n\n## Capability Reuse Register\n\n| Capability | Federal provider | Integration mode | Onboarding status | Cost saving evidence |\n|------------|------------------|-------------------|--------------------|----------------------|\n| [capability] | [provider] | [API / federation / managed service] | [PENDING / IN PROGRESS / LIVE] | [reference] |\n\n## Resource-Efficiency Calculation\n\n| Capability | Reuse baseline cost | Build alternative cost | Lifecycle (years) | Net saving |\n|------------|---------------------|------------------------|--------------------|------------|\n| [capability] | [AED] | [AED] | [n] | [AED] |\n\n| Total programme reuse saving | [AED] |\n|------------------------------|-------|\n\n> Costs include capex, opex, and decommissioning. State the discount rate and the assumptions under each calculation.\n\n## Feasibility & Pilot Plan\n\n| Capability | Feasibility assessment | Pilot scope | Pilot success criteria | Phased rollout sequence |\n|------------|------------------------|-------------|------------------------|--------------------------|\n| [capability] | [Green / Amber / Red — rationale] | [scope] | [criteria] | [phase 1 → 2 → 3] |\n\n## External References\n\n### Document Register\n\n| Doc ID | Title | URL | Verified date |\n|--------|-------|-----|---------------|\n| UAE-CAB-2026-04-23 | UAE Cabinet meeting — Federal Government Guide to Aligning Digital Government Projects with National Priorities | | [YYYY-MM-DD] |\n| UAE-WTU-2031 | We the UAE 2031 vision | | [YYYY-MM-DD] |\n| UAE-AI-2031 | UAE Strategy for Artificial Intelligence 2031 | [URL] | [YYYY-MM-DD] |\n| UAE-NIS-2031 | UAE National Investment Strategy 2031 | [URL] | [YYYY-MM-DD] |\n| UAE-DES | UAE Digital Economy Strategy | [URL] | [YYYY-MM-DD] |\n\n### Citations\n\n| Citation | Doc ID | Section | Used in |\n|----------|--------|---------|---------|\n| [NPRA-1] | UAE-CAB-2026-04-23 | Federal Government Guide | Reuse-vs-Build Justification |\n| [NPRA-2] | UAE-WTU-2031 | [pillar] | Strategic Alignment Matrix |\n| [NPRA-3] | UAE-AI-2031 | [pillar] | Strategic Alignment Matrix |\n| [NPRA-4] | UAE-NIS-2031 | [pillar] | Strategic Alignment Matrix |\n| [NPRA-5] | UAE-DES | [pillar] | Strategic Alignment Matrix |\n\n### Unreferenced Documents\n\n[List any documents read during generation but not cited, or \"None\".]\n\n---\n\n**Generated by**: ArcKit `/arckit.uae-priorities-alignment` command\n**Generated on**: [DATE]\n**ArcKit Version**: [VERSION]\n**Project**: [PROJECT_NAME]\n**Model**: [AI_MODEL]\n", "handoffs": [ {