aw-spec-cli 0.1.5 → 0.1.6

package/assets/.agents/agent.json

@@ -4,7 +4,7 @@
     "type": "google-antigravity",
     "package": "google-antigravity",
     "module": "google.antigravity",
-    "adapter": "../.aw-spec/orchestrator/adapters/google_antigravity.py"
+    "adapter": "../.appweaver/orchestrator/adapters/google_antigravity.py"
   },
   "runtime": "Antigravity CLI (agy -p) — Antigravity is Gemini-based",
   "note": "Antigravity (agy) has no --system-prompt flag, so 'system' is folded into the prompt (system: prepend).",

package/assets/.agents/skills/{aw-spec-orch → appweaver}/SKILL.md

@@ -1,42 +1,42 @@
 ---
-name: "aw-spec-orch"
+name: "appweaver"
 description: "Parametric launcher (Antigravity): run ANY converted aw-spec skill on the aw-orchestrator under one of the 4 strategies (agent [default], spawn, sdk, sdk-apply)."
 argument-hint: "<skill> [strategy] [input…] — e.g. 'select-domain', 'specify spawn Build an order API', 'analyze-slice'"
-compatibility: "Requires .aw-spec/orchestrator/ and the agy CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the agy CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Skill Launcher
 
-Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.aw-spec/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
+Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.appweaver/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
 
-- **Engine + workflows (common, shared by all agents):** `.aw-spec/orchestrator/orchestrator.py`, `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.aw-spec/orchestrator/modules/`, shared scripts in `.aw-spec/scripts/`
+- **Engine + workflows (common, shared by all agents):** `.appweaver/orchestrator/orchestrator.py`, `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.appweaver/orchestrator/modules/`, shared scripts in `.appweaver/scripts/`
 - **This agent's transport profile:** `.agents/agent.json`
 
   > Antigravity spawns via the `agy` CLI (Gemini-based; no `--system-prompt`,
   > so `system` is folded into the prompt — isolation is best-effort). Its
   > `sdk` block declares the SDK the `sdk`/`sdk-apply` strategies import
   > (`google-antigravity`) and the adapter
-  > (`.aw-spec/orchestrator/adapters/google_antigravity.py`, shared per-SDK)
+  > (`.appweaver/orchestrator/adapters/google_antigravity.py`, shared per-SDK)
   > that owns its calling convention.
 
 ## Execution Steps
 
 1. **Parse Arguments** (`<skill> [strategy] [input…]`):
-   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
+   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
    - `strategy` (optional, one of `agent`, `spawn`, `sdk`, `sdk-apply`; default `agent` — YOU fulfill each generation through the checkpoint channel, no profile needed): who executes each generation. Always pass `--strategy <strategy>`.
    - Everything after the strategy is the user input: pass it as `--input "<text>"` (omit when empty).
    - `--agent-profile .agents/agent.json` is required for `spawn`, `sdk`, and `sdk-apply` (`agent` needs no profile). If the SDK package isn't installed, add `--sdk-install`.
-   - **Always** pass `--checkpoint .aw-spec/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
+   - **Always** pass `--checkpoint .appweaver/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
    - `spawn` may also add `--isolation bare|fresh` and `--model <name>`; `sdk`/`sdk-apply` accept `--model <name>`.
 
 2. **Run the Interpreter**:
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
      --strategy <strategy> \
-     --checkpoint .aw-spec/orchestrator/.state/<skill>.state.json \
+     --checkpoint .appweaver/orchestrator/.state/<skill>.state.json \
      [--agent-profile .agents/agent.json]   # spawn, sdk, sdk-apply \
      [--input "<user input>"] \
      --json

package/assets/.agents/skills/{aw-spec-orch-demo → appweaver-demo}/SKILL.md

@@ -1,23 +1,23 @@
 ---
-name: "aw-spec-orch-demo"
+name: "appweaver-demo"
 description: "Prototype launcher (Antigravity): run the aw-orchestrator using the specified strategy (spawn, agent, sdk, sdk-apply)."
 argument-hint: "Optional strategy ('agent', 'spawn', 'sdk', 'sdk-apply') and/or k=value vars (e.g. 'agent out_dir=...')"
-compatibility: "Requires .aw-spec/orchestrator/ and the gemini CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the gemini CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Launcher
 
-All orchestration lives in the workflow YAML and is executed by `.aw-spec/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
+All orchestration lives in the workflow YAML and is executed by `.appweaver/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
 
-- **Engine + workflow (general):** `.aw-spec/orchestrator/orchestrator.py`, `*.orch.yaml`
+- **Engine + workflow (general):** `.appweaver/orchestrator/orchestrator.py`, `*.orch.yaml`
 - **This agent's transport profile:** `.agents/agent.json`
 
   > Antigravity spawns via the `agy` CLI (Gemini-based; no `--system-prompt`, so
   > `system` is folded into the prompt). Its `sdk` block declares the SDK the
   > `sdk`/`sdk-apply` strategies import (`google-antigravity`) and the adapter
-  > (`.aw-spec/orchestrator/adapters/google_antigravity.py`, shared per-SDK)
+  > (`.appweaver/orchestrator/adapters/google_antigravity.py`, shared per-SDK)
   > that owns its calling convention.
 
 ## Execution Steps
@@ -30,7 +30,7 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
      package/module (and its `adapter` file) to import from its `sdk` block.
      If the SDK package isn't installed, add `--sdk-install` so the engine
      pip-installs the declared package first. (`agent` needs no profile.)
-   - `--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json` is required for
+   - `--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json` is required for
      `sdk-apply` and `agent` (suspend/resume — follow the loop in step 3).
    - `spawn` accepts `--model <name>` (e.g. `gemini-2.5-pro`); isolation is
      best-effort for Antigravity (no `--bare` equivalent). `sdk`/`sdk-apply`
@@ -39,11 +39,11 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
 2. **Run the Interpreter**:
    Run the command (include only the bracketed flags that apply to the chosen strategy):
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-demo.orch.yaml \
      --strategy <strategy> \
      [--agent-profile .agents/agent.json]   # spawn, sdk, sdk-apply \
-     [--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
+     [--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
      --json
    ```
 

package/assets/.claude/agent.json

@@ -4,7 +4,7 @@
     "type": "claude-agent-sdk",
     "package": "claude-agent-sdk",
     "module": "claude_agent_sdk",
-    "adapter": "../.aw-spec/orchestrator/adapters/claude_agent_sdk.py"
+    "adapter": "../.appweaver/orchestrator/adapters/claude_agent_sdk.py"
   },
   "runtime": "Claude Code CLI (claude -p)",
   "bin": "claude",

package/assets/.claude/skills/{aw-spec-orch → appweaver}/SKILL.md

@@ -1,41 +1,41 @@
 ---
-name: "aw-spec-orch"
+name: "appweaver"
 description: "Parametric launcher (Claude Code): run ANY converted aw-spec skill on the aw-orchestrator under one of the 4 strategies (agent [default], spawn, sdk, sdk-apply)."
 argument-hint: "<skill> [strategy] [input…] — e.g. 'select-domain', 'specify spawn Build an order API', 'analyze-slice'"
-compatibility: "Requires .aw-spec/orchestrator/ and the claude CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the claude CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Skill Launcher
 
-Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.aw-spec/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
+Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.appweaver/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
 
-- **Engine + workflows (common, shared by all agents):** `.aw-spec/orchestrator/orchestrator.py`, `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.aw-spec/orchestrator/modules/`, shared scripts in `.aw-spec/scripts/`
+- **Engine + workflows (common, shared by all agents):** `.appweaver/orchestrator/orchestrator.py`, `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.appweaver/orchestrator/modules/`, shared scripts in `.appweaver/scripts/`
 - **This agent's transport profile:** `.claude/agent.json`
 
   > Claude Code spawns via the `claude -p` CLI (native `--system-prompt`,
   > `--tools`, and `--bare` isolation). Its `sdk` block declares the SDK the
   > `sdk`/`sdk-apply` strategies import (`claude-agent-sdk`) and the adapter
-  > (`.aw-spec/orchestrator/adapters/claude_agent_sdk.py`, shared per-SDK)
+  > (`.appweaver/orchestrator/adapters/claude_agent_sdk.py`, shared per-SDK)
   > that owns its calling convention.
 
 ## Execution Steps
 
 1. **Parse Arguments** (`<skill> [strategy] [input…]`):
-   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
+   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
    - `strategy` (optional, one of `agent`, `spawn`, `sdk`, `sdk-apply`; default `agent` — YOU fulfill each generation through the checkpoint channel, no profile needed): who executes each generation. Always pass `--strategy <strategy>`.
    - Everything after the strategy is the user input: pass it as `--input "<text>"` (omit when empty).
    - `--agent-profile .claude/agent.json` is required for `spawn`, `sdk`, and `sdk-apply` (`agent` needs no profile). If the SDK package isn't installed, add `--sdk-install`.
-   - **Always** pass `--checkpoint .aw-spec/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
+   - **Always** pass `--checkpoint .appweaver/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
    - `spawn` may also add `--isolation bare|fresh` and `--model <name>`; `sdk`/`sdk-apply` accept `--model <name>`.
 
 2. **Run the Interpreter**:
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
      --strategy <strategy> \
-     --checkpoint .aw-spec/orchestrator/.state/<skill>.state.json \
+     --checkpoint .appweaver/orchestrator/.state/<skill>.state.json \
      [--agent-profile .claude/agent.json]   # spawn, sdk, sdk-apply \
      [--input "<user input>"] \
      --json

package/assets/.claude/skills/{aw-spec-orch-demo → appweaver-demo}/SKILL.md

@@ -1,23 +1,23 @@
 ---
-name: "aw-spec-orch-demo"
+name: "appweaver-demo"
 description: "Prototype launcher (Claude Code): run the aw-orchestrator using the specified strategy (spawn, agent, sdk, sdk-apply)."
 argument-hint: "Optional strategy ('agent', 'spawn', 'sdk', 'sdk-apply') and/or k=value vars (e.g. 'agent out_dir=...')"
-compatibility: "Requires .aw-spec/orchestrator/ and the claude CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the claude CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Launcher
 
-All orchestration lives in the workflow YAML and is executed by `.aw-spec/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
+All orchestration lives in the workflow YAML and is executed by `.appweaver/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
 
-- **Engine + workflow (general):** `.aw-spec/orchestrator/orchestrator.py`, `*.orch.yaml`
+- **Engine + workflow (general):** `.appweaver/orchestrator/orchestrator.py`, `*.orch.yaml`
 - **This agent's transport profile:** `.claude/agent.json`
 
   > Claude Code spawns via the `claude -p` CLI (native `--system-prompt`,
   > `--tools`, and `--bare` isolation). Its `sdk` block declares the SDK the
   > `sdk`/`sdk-apply` strategies import (`claude-agent-sdk`) and the adapter
-  > (`.aw-spec/orchestrator/adapters/claude_agent_sdk.py`, shared per-SDK)
+  > (`.appweaver/orchestrator/adapters/claude_agent_sdk.py`, shared per-SDK)
   > that owns its calling convention.
 
 ## Execution Steps
@@ -30,7 +30,7 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
      package/module (and its `adapter` file) to import from its `sdk` block.
      If the SDK package isn't installed, add `--sdk-install` so the engine
      pip-installs the declared package first. (`agent` needs no profile.)
-   - `--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json` is required for
+   - `--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json` is required for
      `sdk-apply` and `agent` (suspend/resume — follow the loop in step 3).
    - `spawn` may also add `--isolation bare|fresh` and `--model <name>` (bare is
      strongest; use it when `ANTHROPIC_API_KEY` is set). `sdk`/`sdk-apply` accept
@@ -39,11 +39,11 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
 2. **Run the Interpreter**:
    Run the command (include only the bracketed flags that apply to the chosen strategy):
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-demo.orch.yaml \
      --strategy <strategy> \
      [--agent-profile .claude/agent.json]   # spawn, sdk, sdk-apply \
-     [--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
+     [--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
      --json
    ```
 

package/assets/.kilocode/agent.json

@@ -4,7 +4,7 @@
     "type": "claude-agent-sdk",
     "package": "claude-agent-sdk",
     "module": "claude_agent_sdk",
-    "adapter": "../.aw-spec/orchestrator/adapters/claude_agent_sdk.py"
+    "adapter": "../.appweaver/orchestrator/adapters/claude_agent_sdk.py"
   },
   "runtime": "Kilo Code launches the interpreter; generation delegates to the Claude Code CLI",
   "note": "Kilo Code is a VS Code extension with no standalone headless generation CLI, so this profile reuses `claude -p` for the fresh generation. To generate via Gemini instead, replace bin/args/system/user/tools_flag/approval with the .agents (antigravity) profile's values.",

package/assets/.kilocode/workflows/{aw-spec-orch-demo.md → appweaver-demo.md}

@@ -1,23 +1,23 @@
 ---
-name: "aw-spec-orch-demo"
+name: "appweaver-demo"
 description: "Prototype launcher (Kilo Code): run the aw-orchestrator using the specified strategy (spawn, agent, sdk, sdk-apply)."
 argument-hint: "Optional strategy ('agent', 'spawn', 'sdk', 'sdk-apply') and/or k=value vars (e.g. 'agent out_dir=...')"
-compatibility: "Requires .aw-spec/orchestrator/ and the claude CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the claude CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Launcher
 
-All orchestration lives in the workflow YAML and is executed by `.aw-spec/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
+All orchestration lives in the workflow YAML and is executed by `.appweaver/orchestrator/orchestrator.py` (the general, agent-agnostic engine). The interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself.
 
-- **Engine + workflow (general):** `.aw-spec/orchestrator/orchestrator.py`, `*.orch.yaml`
+- **Engine + workflow (general):** `.appweaver/orchestrator/orchestrator.py`, `*.orch.yaml`
 - **This agent's transport profile:** `.kilocode/agent.json`
 
   > Kilo Code has no native headless CLI, so it reuses `claude -p` for `spawn`
   > (native `--system-prompt`, `--tools`, `--bare` isolation). Its `sdk` block
   > declares the SDK the `sdk`/`sdk-apply` strategies import (`claude-agent-sdk`)
-  > and the adapter (`.aw-spec/orchestrator/adapters/claude_agent_sdk.py`,
+  > and the adapter (`.appweaver/orchestrator/adapters/claude_agent_sdk.py`,
   > shared per-SDK) that owns its calling convention.
 
 ## Execution Steps
@@ -30,7 +30,7 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
      package/module (and its `adapter` file) to import from its `sdk` block.
      If the SDK package isn't installed, add `--sdk-install` so the engine
      pip-installs the declared package first. (`agent` needs no profile.)
-   - `--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json` is required for
+   - `--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json` is required for
      `sdk-apply` and `agent` (suspend/resume — follow the loop in step 3).
    - `spawn` may also add `--isolation bare|fresh` and `--model <name>` (bare is
      strongest; use it when `ANTHROPIC_API_KEY` is set). `sdk`/`sdk-apply` accept
@@ -39,11 +39,11 @@ All orchestration lives in the workflow YAML and is executed by `.aw-spec/orches
 2. **Run the Interpreter**:
    Run the command (include only the bracketed flags that apply to the chosen strategy):
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-demo.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-demo.orch.yaml \
      --strategy <strategy> \
      [--agent-profile .kilocode/agent.json]   # spawn, sdk, sdk-apply \
-     [--checkpoint .aw-spec/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
+     [--checkpoint .appweaver/orchestrator/.demo-out/demo.state.json]  # sdk-apply, agent \
      --json
    ```
 

package/assets/.kilocode/workflows/{aw-spec-orch.md → appweaver.md}

@@ -1,41 +1,41 @@
 ---
-name: "aw-spec-orch"
+name: "appweaver"
 description: "Parametric launcher (Kilo Code): run ANY converted aw-spec skill on the aw-orchestrator under one of the 4 strategies (agent [default], spawn, sdk, sdk-apply)."
 argument-hint: "<skill> [strategy] [input…] — e.g. 'select-domain', 'specify spawn Build an order API', 'analyze-slice'"
-compatibility: "Requires .aw-spec/orchestrator/ and the claude CLI on PATH"
+compatibility: "Requires .appweaver/orchestrator/ and the claude CLI on PATH"
 user-invocable: true
 disable-model-invocation: false
 ---
 
 # Orchestrator Skill Launcher
 
-Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.aw-spec/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
+Runs one converted `aw-spec-*` workflow on the shared, agent-agnostic engine. All orchestration and **all context management live in the workflow YAML + engine** (`.appweaver/orchestrator/orchestrator.py`): the interpreter assembles the COMPLETE payload (system + user) for every request; you never author generation context yourself. Execution follows the chosen strategy; the checkpoint channel carries every human-facing interaction regardless of strategy.
 
-- **Engine + workflows (common, shared by all agents):** `.aw-spec/orchestrator/orchestrator.py`, `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.aw-spec/orchestrator/modules/`, shared scripts in `.aw-spec/scripts/`
+- **Engine + workflows (common, shared by all agents):** `.appweaver/orchestrator/orchestrator.py`, `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`, shared modules in `.appweaver/orchestrator/modules/`, shared scripts in `.appweaver/scripts/`
 - **This agent's transport profile:** `.kilocode/agent.json`
 
   > Kilo Code has no native headless CLI, so it reuses `claude -p` for `spawn`
   > (native `--system-prompt`, `--tools`, `--bare` isolation). Its `sdk` block
   > declares the SDK the `sdk`/`sdk-apply` strategies import (`claude-agent-sdk`)
-  > and the adapter (`.aw-spec/orchestrator/adapters/claude_agent_sdk.py`,
+  > and the adapter (`.appweaver/orchestrator/adapters/claude_agent_sdk.py`,
   > shared per-SDK) that owns its calling convention.
 
 ## Execution Steps
 
 1. **Parse Arguments** (`<skill> [strategy] [input…]`):
-   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
+   - `skill` (required): the aw-spec skill name, e.g. `demo`, `select-domain`, `foundation`, `specify`, `design`, `implement`, `build`. Resolve the workflow file `.appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml`. If it does not exist, list the available `aw-spec-*.orch.yaml` files in that folder and stop.
    - `strategy` (optional, one of `agent`, `spawn`, `sdk`, `sdk-apply`; default `agent` — YOU fulfill each generation through the checkpoint channel, no profile needed): who executes each generation. Always pass `--strategy <strategy>`.
    - Everything after the strategy is the user input: pass it as `--input "<text>"` (omit when empty).
    - `--agent-profile .kilocode/agent.json` is required for `spawn`, `sdk`, and `sdk-apply` (`agent` needs no profile). If the SDK package isn't installed, add `--sdk-install`.
-   - **Always** pass `--checkpoint .aw-spec/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
+   - **Always** pass `--checkpoint .appweaver/orchestrator/.state/<skill>.state.json` — for EVERY strategy. Converted skills contain interactive steps (questions, selections, hooks); the checkpoint is how they reach you and the user. Strategies only govern who generates.
    - `spawn` may also add `--isolation bare|fresh` and `--model <name>`; `sdk`/`sdk-apply` accept `--model <name>`.
 
 2. **Run the Interpreter**:
    ```bash
-   python3 .aw-spec/orchestrator/orchestrator.py \
-     .aw-spec/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
+   python3 .appweaver/orchestrator/orchestrator.py \
+     .appweaver/orchestrator/workflows/aw-spec-<skill>.orch.yaml \
      --strategy <strategy> \
-     --checkpoint .aw-spec/orchestrator/.state/<skill>.state.json \
+     --checkpoint .appweaver/orchestrator/.state/<skill>.state.json \
      [--agent-profile .kilocode/agent.json]   # spawn, sdk, sdk-apply \
      [--input "<user input>"] \
      --json

package/assets/docs/pharma-constitution.my-ref.md

@@ -0,0 +1,86 @@
+# Pharma Constitution — Domain Addenda
+
+> **Domain addenda to the technology constitution.** Not ratified on its own — compose it with
+> the technology base.
+
+## How to use (compose-at-ratification)
+
+The technology base (`docs/technology-constitution.md`) **auto-loads** for `/aw-spec-constitution`,
+so you pass only this domain addenda:
+
+```
+/aw-spec-constitution @docs/pharma-constitution.md
+```
+
+This file supplies **only** the pharma deltas: project identity, regulatory posture, the pharma
+domain principles (which **continue** the technology numbering at **XVI**), folder additions,
+governance overrides, and the active-domain pointer. The reusable principles I–XV live in the
+technology base and are not repeated here.
+
+Active domain folder: `docs/domainspecs/pharma/` (set via `/aw-spec-select-domain pharma`).
+
+## Project Identity (fills the technology base)
+
+- **Project name:** `<SampleProjectName>` — Medicinal Product Registry (Headless API).
+- **Mission:** maintain a centralized, authoritative registry of medicinal products in compliance with pharmaceutical industry standards, regulatory requirements, and healthcare interoperability specifications; exposed as a headless HTTP + FHIR API ready for integration with prescribing, dispensing, manufacturing, pharmacovigilance, and clinical systems.
+- **Bounded contexts (modules):** enumerated in `docs/domainspecs/pharma/domain-requirements.md` (project-specific).
+- **Architecture posture:** Modular Monolith with Clean Architecture + DDD; `MedicinalProduct` is the Aggregate Root; each module designed for clean extraction into an independent microservice. **HEADLESS.**
+
+## Regulatory Posture
+
+Built for regulatory compliance **readiness** — auditability, traceability, data integrity, and
+provenance are designed in. Data-integrity expectations follow **ALCOA+** for GxP-relevant
+product records. Identifier standards (NDC), substance identity (UNII), classification (WHO
+ATC), and ISO IDMP concept alignment are first-class. Data residency configurable per deployment.
+
+## Domain Principles
+
+> Extend the technology Core Principles; numbering **continues from XV**.
+
+### XVI — Pharmaceutical Product Identification (NON-NEGOTIABLE)
+NDC modeled as a Value Object with discrete Labeler/Product/Package segments; NDC uniqueness enforced (aggregate + persistence constraint); NDC validation rules configurable; no invented NDC/Labeler codes. The domain model aligns with ISO IDMP concepts (Medicinal Product, Manufactured Item, Pharmaceutical Product, Substance, MAH, Packaging, Strength, Route of Administration).
+→ `docs/domainspecs/pharma/ndc.md`, `idmp.md`
+
+### XVII — Pharma Terminology & Classification (NON-NEGOTIABLE)
+Coded data uses standard terminologies — UNII (substances), RxNorm (clinical drug), SNOMED CT (dose form / route / classification), UCUM (units), and WHO ATC (therapeutic classification). Every coded field is a Codeable value object; lookup/validation via the Terminology module; ATC codes validated against configured code sets (multiple ATC per product allowed); no invented or free-text codes.
+→ `docs/domainspecs/pharma/terminology.md`, `atc.md`
+
+### XVIII — Regulatory Compliance: Audit, Provenance & Versioning (NON-NEGOTIABLE)
+Immutable audit records (User, Timestamp, Action, Previous Value, New Value) for product creation, modification, retirement, identifier changes, and classification changes; `AuditRecord` is append-only. Provenance captured for externally sourced product data (source, method, agent, timestamp). Full version history of product information; historical versions remain queryable. Extends technology **X** and **XIV** with pharma compliance controls.
+→ `docs/domainspecs/pharma/regulatory-compliance.md`, `data-provenance.md`, `auditing.domain.md`, `persistence.domain.md`
+
+### XIX — Medicinal Product Lifecycle Integrity (NON-NEGOTIABLE)
+MedicinalProduct lifecycle (Draft → Under Review → Approved → Active → Discontinued/Withdrawn) is a guarded state machine; only valid transitions are permitted; registration completeness (required attributes, ≥ 1 active ingredient, ≥ 1 packaging, valid NDC/dosage-form/route/ATC) is enforced before leaving Draft; retirement is a logical state change, never a hard delete. Each transition emits a domain event and is audit-mandatory.
+→ `docs/domainspecs/pharma/product-lifecycle.domain.md`, `domain-driven-design.domain.md`, `eventing.domain.md`
+
+### XX — Healthcare Interoperability Readiness
+The model maps to FHIR Medication / MedicationKnowledge / Substance / Organization (projections, not the system of record); product identifiers map to FHIR Identifier; coded fields map to CodeableConcept/Coding; the solution supports future HL7-based integration via Interop adapters. Extends technology **XII** and **XIV** with the FHIR contract.
+→ `docs/domainspecs/pharma/fhir.md`, `hl7.md`
+
+## Folder Structure Additions
+
+- Pharma additions (Interop/Fhir + Hl7v2 adapters, InteropTests, terminology seed fixtures, provenance/version-history stores): `docs/domainspecs/pharma/folder-structure.domain.md`
+
+## Security & Governance Addenda
+
+- **Change authority** (who may register / approve / retire products, and change identifiers or classification): `docs/domainspecs/pharma/authorization.domain.md`
+- **Data classification** (public vs commercially-sensitive / pre-market / externally-sourced; GxP/ALCOA+ integrity): `docs/domainspecs/pharma/data-classification.domain.md`
+- **Zero-trust posture** (transport, scope/trace propagation, change-authority enforcement): `docs/domainspecs/pharma/zero-trust.domain.md`
+- **Coding standards** (forbidden patterns, quality gates): `docs/domainspecs/pharma/coding-standards.domain.md`
+- **API/contract versioning** (FHIR + NDC identifier stability): `docs/domainspecs/pharma/api-versioning.domain.md`
+- **Dependency policy** (FHIR SDK, terminology libraries, regulatory suitability): `docs/domainspecs/pharma/dependency-policy.domain.md`
+
+## AI Rules Addenda
+
+- Identifier/code safety (no invented NDC/UNII/RxNorm/SNOMED/ATC), projection discipline, lifecycle/audit edit limits, pharma refusal conditions: `docs/domainspecs/pharma/ai-rules.domain.md` (extends `docs/glossary/ai-rules.md`)
+
+## Governance Overrides
+
+- Mandatory approver for any identifier (NDC), classification (ATC), or lifecycle-rule change: Regulatory/Compliance Officer (in addition to a Principal Engineer and a Domain Owner). Change-authority roles are defined in `docs/domainspecs/pharma/authorization.domain.md`.
+- Additional review required after every relevant regulatory or terminology-release update (e.g. WHO ATC annual update, FDA NDC directory changes).
+- **Versioning note:** any change to NDC identity rules, the lifecycle state machine, the audit-record shape, or the canonical FHIR interoperability surface is a MAJOR bump.
+
+## Domain Requirements Pointer
+
+→ `docs/domainspecs/pharma/domain-requirements.md`
+(`[DOMAIN: Bounded Contexts / Modules]`, per-subsection pointers, `[DOMAIN: Platform Topology]`, `[DOMAIN: Governance Overrides]`).

package/dist/utils/paths.js

@@ -14,7 +14,7 @@ export async function resolveAssetsPath() {
         return distAssets;
     }
     // Development mode: use the source AppWeaver.Spec repo
-    const sourceRepo = path.resolve(__dirname, '../../../AppWeaver.Spec.Orchestration');
+    const sourceRepo = path.resolve(__dirname, '../../../AppWeaver.Spec');
     if (await fs.pathExists(sourceRepo)) {
         return sourceRepo;
     }
@@ -31,6 +31,6 @@ export async function resolveAssetsPath() {
  * Get the source AppWeaver.Spec repository path (for bundling script)
  */
 export function getSourceRepoPath() {
-    return path.resolve(__dirname, '../../AppWeaver.Spec.Orchestration');
+    return path.resolve(__dirname, '../../AppWeaver.Spec');
 }
 //# sourceMappingURL=paths.js.map

package/dist/utils/paths.js.map

@@ -1 +1 @@
-{"version":3,"file":"paths.js","sourceRoot":"","sources":["../../src/utils/paths.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AACpC,OAAO,EAAE,MAAM,UAAU,CAAC;AAE1B,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAE/D;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB;IACrC,oEAAoE;IACpE,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,cAAc,CAAC,CAAC;IAC3D,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;QACpC,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,uDAAuD;IACvD,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,uCAAuC,CAAC,CAAC;IACpF,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;QACpC,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,2CAA2C;IAC3C,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;IACjD,MAAM,SAAS,GAAG,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;IAC/C,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QACnC,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,IAAI,KAAK,CACb,0CAA0C;QAC1C,UAAU,UAAU,KAAK,UAAU,KAAK,SAAS,EAAE,CACpD,CAAC;AACJ,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,iBAAiB;IAC/B,OAAO,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,oCAAoC,CAAC,CAAC;AACvE,CAAC"}
+{"version":3,"file":"paths.js","sourceRoot":"","sources":["../../src/utils/paths.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,aAAa,EAAE,MAAM,KAAK,CAAC;AACpC,OAAO,EAAE,MAAM,UAAU,CAAC;AAE1B,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAE/D;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB;IACrC,oEAAoE;IACpE,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,cAAc,CAAC,CAAC;IAC3D,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;QACpC,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,uDAAuD;IACvD,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,yBAAyB,CAAC,CAAC;IACtE,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;QACpC,OAAO,UAAU,CAAC;IACpB,CAAC;IAED,2CAA2C;IAC3C,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;IACjD,MAAM,SAAS,GAAG,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;IAC/C,IAAI,MAAM,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QACnC,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,IAAI,KAAK,CACb,0CAA0C;QAC1C,UAAU,UAAU,KAAK,UAAU,KAAK,SAAS,EAAE,CACpD,CAAC;AACJ,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,iBAAiB;IAC/B,OAAO,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,sBAAsB,CAAC,CAAC;AACzD,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aw-spec-cli",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "AppWeaver Spec-Driven Development CLI - scaffolds projects with vertical slices, DDD, CQRS, and agent skills",
   "type": "module",
   "main": "dist/index.js",