prizmkit 1.1.77 → 1.1.78

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.77",
-  "bundledAt": "2026-06-14T15:13:42.592Z",
-  "bundledFrom": "2327b8b"
+  "frameworkVersion": "1.1.78",
+  "bundledAt": "2026-06-14T15:40:03.496Z",
+  "bundledFrom": "190a723"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.77",
+  "version": "1.1.78",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -152,7 +152,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout and stop-on-failure options
+   - Yes — Configure session timeout, stop-on-failure, and reasoning effort options
 
    Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
 
@@ -172,6 +172,14 @@ Detect user intent from their message, then follow the corresponding workflow:
    - No (default) — Skip deployment after pipeline completes
    - Yes — Run /prizmkit-deploy automatically after all bugs fixed successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any bug was not fixed (status not 'completed', 'skipped', or 'needs_info').
 
+   **Question 4 — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    **Environment variable mapping** (for translating user responses → env vars):
 
    | Config choice | Environment variable |
@@ -183,13 +191,13 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
    | Deploy: Yes | `ENABLE_DEPLOY=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
    | Variable | Default | Purpose |
    |----------|---------|---------|
    | `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
-   | `PRIZMKIT_EFFORT` | (none) | AI reasoning effort: `low`\|`medium`\|`high`\|`xhigh`\|`max` (max = Claude Code only) |
    | `AUTO_PUSH` | `0` | Auto-push to remote after successful bug fix (`1` to enable) |
    | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `bugfix/pipeline-{run_id}`) |
    | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
@@ -208,7 +216,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
+   VERBOSE=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
    ```
 

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -169,7 +169,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout, stop-on-failure, and deploy-after-completion options
+   - Yes — Configure session timeout, stop-on-failure, deploy-after-completion, and reasoning effort options
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 
@@ -189,6 +189,14 @@ Detect user intent from their message, then follow the corresponding workflow:
    - No (default) — Skip deployment after pipeline completes
    - Yes — Run /prizmkit-deploy automatically after all features complete successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any feature did not complete successfully (status not 'completed' or manually 'skipped').
 
+   **Question 4 — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    **Environment variable mapping** (for translating user responses → env vars):
 
    | Config choice | Environment variable |
@@ -200,13 +208,13 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
    | Deploy: Yes | `ENABLE_DEPLOY=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
    | Variable | Default | Purpose |
    |----------|---------|---------|
    | `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
-   | `PRIZMKIT_EFFORT` | (none) | AI reasoning effort: `low`\|`medium`\|`high`\|`xhigh`\|`max` (max = Claude Code only) |
    | `AUTO_PUSH` | `0` | Auto-push to remote after successful feature (`1` to enable) |
    | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `dev/{feature_id}-YYYYMMDDHHmm`) |
    | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
@@ -226,7 +234,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
+   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 
@@ -237,7 +245,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    With all options:
    ```bash
    .prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --features F-001:F-005 \
-     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1"
+     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -170,7 +170,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for critic review, session timeout, and failure behavior
-   - Yes — Configure critic review, session timeout, and stop-on-failure options
+   - Yes — Configure critic review, session timeout, stop-on-failure, and reasoning effort options
 
    Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
 
@@ -196,6 +196,16 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    Default Critic to Off unless refactor items have `priority: "critical"` (in which case default to On).
 
+   **If advanced config was selected, also ask about reasoning effort** in a follow-up `AskUserQuestion` call:
+
+   **Question — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    **Environment variable mapping** (for translating user responses → env vars):
 
    | Config choice | Environment variable |
@@ -209,13 +219,13 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
    | Deploy: Yes | `ENABLE_DEPLOY=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
    | Variable | Default | Purpose |
    |----------|---------|---------|
    | `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
-   | `PRIZMKIT_EFFORT` | (none) | AI reasoning effort: `low`\|`medium`\|`high`\|`xhigh`\|`max` (max = Claude Code only) |
    | `AUTO_PUSH` | `0` | Auto-push to remote after successful refactor (`1` to enable) |
    | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `refactor/pipeline-{run_id}`) |
    | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
@@ -234,7 +244,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
 

package/bundled/skills-windows/bugfix-pipeline-launcher/SKILL.md

@@ -177,7 +177,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout and stop-on-failure options
+   - Yes — Configure session timeout, stop-on-failure, and reasoning effort options
 
    Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
 
@@ -193,6 +193,14 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Off (default) — Pipeline continues to next task after failure
    - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
+   **Question 3 — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    **Environment variable mapping** (for translating user responses → env vars):
 
    | Config choice | Environment variable |
@@ -203,6 +211,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Critic: On | `ENABLE_CRITIC=true` |
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -220,7 +229,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"
+   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-bugfix.ps1 run .prizmkit/plans/bug-fix-list.json
    ```
 
@@ -231,7 +240,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    With all options:
    ```powershell
    .\.prizmkit\dev-pipeline\launch-bugfix-daemon.ps1 start .prizmkit/plans/bug-fix-list.json `
-     --env "VERBOSE=1 MAX_RETRIES=5"
+     --env "VERBOSE=1 MAX_RETRIES=5 PRIZMKIT_EFFORT=high"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 7.

package/bundled/skills-windows/feature-pipeline-launcher/SKILL.md

@@ -195,7 +195,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 4 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout and stop-on-failure options
+   - Yes — Configure session timeout, stop-on-failure, and reasoning effort options
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 
@@ -211,6 +211,14 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Off (default) — Pipeline continues to next task after failure
    - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
+   **Question 3 — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    **Environment variable mapping** (for translating user responses → env vars):
 
    | Config choice | Environment variable |
@@ -221,6 +229,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Max retries: N | `MAX_RETRIES=N` |
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -239,7 +248,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:ENABLE_CRITIC = "true"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"
+   $env:VERBOSE = "1"; $env:ENABLE_CRITIC = "true"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-feature.ps1 run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 
@@ -250,7 +259,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    With all options:
    ```powershell
    .\.prizmkit\dev-pipeline\launch-feature-daemon.ps1 start .prizmkit/plans/feature-list.json --features F-001:F-005 `
-     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5"
+     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 PRIZMKIT_EFFORT=high"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.

package/bundled/skills-windows/refactor-pipeline-launcher/SKILL.md

@@ -192,7 +192,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 3 — Advanced config?** (multiSelect: false):
    - No (default) — Use defaults for critic review, session timeout, and failure behavior
-   - Yes — Configure critic review, session timeout, and stop-on-failure options
+   - Yes — Configure critic review, session timeout, stop-on-failure, and reasoning effort options
 
    Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
 
@@ -212,6 +212,14 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Off (default) — Skip adversarial review
    - On — Enable adversarial critic review: an independent AI agent reviews the refactor plan for completeness and the implementation for regressions, missing edge cases, and behavior violations. Adds ~5-10 min per refactor task.
 
+   **Question 4 — Reasoning effort** (multiSelect: false):
+   - Default (none) — Use CLI default
+   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
    Default Critic to Off unless refactor items have `priority: "critical"` (in which case default to On).
 
    **Environment variable mapping** (for translating user responses → env vars):
@@ -224,6 +232,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Critic: On | `ENABLE_CRITIC=true` |
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Stop on failure: On | `STOP_ON_FAILURE=1` |
+   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -241,7 +250,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"
+   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-refactor.ps1 run .prizmkit/plans/refactor-list.json
    ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.77",
+  "version": "1.1.78",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {