prizmkit 1.1.193 → 1.1.195

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (79) hide show
  1. package/bin/create-prizmkit.js +43 -12
  2. package/bundled/VERSION.json +3 -3
  3. package/bundled/dev-pipeline/.env.example +5 -0
  4. package/bundled/dev-pipeline/README.md +2 -1
  5. package/bundled/dev-pipeline/prizmkit_runtime/checkpoint_state.py +111 -30
  6. package/bundled/dev-pipeline/prizmkit_runtime/cli.py +44 -3
  7. package/bundled/dev-pipeline/prizmkit_runtime/commands.py +29 -9
  8. package/bundled/dev-pipeline/prizmkit_runtime/config.py +121 -44
  9. package/bundled/dev-pipeline/prizmkit_runtime/daemon.py +190 -37
  10. package/bundled/dev-pipeline/prizmkit_runtime/interoperability.py +1 -0
  11. package/bundled/dev-pipeline/prizmkit_runtime/iterate.py +2480 -0
  12. package/bundled/dev-pipeline/prizmkit_runtime/paths.py +3 -0
  13. package/bundled/dev-pipeline/prizmkit_runtime/runner_bookkeeping.py +32 -8
  14. package/bundled/dev-pipeline/prizmkit_runtime/runners.py +29 -12
  15. package/bundled/dev-pipeline/prizmkit_runtime/runtime_commit.py +13 -5
  16. package/bundled/dev-pipeline/prizmkit_runtime/status.py +166 -0
  17. package/bundled/dev-pipeline/scripts/feature_list_contract.py +964 -0
  18. package/bundled/dev-pipeline/scripts/generate-bootstrap-prompt.py +18 -40
  19. package/bundled/dev-pipeline/scripts/generate-bugfix-prompt.py +24 -19
  20. package/bundled/dev-pipeline/scripts/prompt_framework.py +24 -8
  21. package/bundled/dev-pipeline/templates/bootstrap-tier3.md +1 -63
  22. package/bundled/dev-pipeline/templates/bug-fix-list-schema.json +8 -6
  23. package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md +0 -10
  24. package/bundled/dev-pipeline/templates/feature-list-schema.json +8 -6
  25. package/bundled/dev-pipeline/templates/iterate/evaluate-prompt.md +97 -0
  26. package/bundled/dev-pipeline/templates/iterate/evaluation-schema.json +538 -0
  27. package/bundled/dev-pipeline/templates/iterate/headless-plan-prompt.md +66 -0
  28. package/bundled/dev-pipeline/templates/sections/phase-specify-plan-full.md +2 -2
  29. package/bundled/dev-pipeline/templates/sections/runtime-commit-handoff.md +13 -4
  30. package/bundled/rules/USAGE.md +15 -48
  31. package/bundled/rules/_rules-metadata.json +7 -14
  32. package/bundled/rules/general/coding-baseline.md +23 -0
  33. package/bundled/rules/prizm/prizm-progressive-loading.md +2 -2
  34. package/bundled/skills/_metadata.json +12 -42
  35. package/bundled/skills/app-planner/SKILL.md +2 -2
  36. package/bundled/skills/app-planner/references/generated-plan-review.md +2 -2
  37. package/bundled/skills/app-planner/references/project-state-detection.md +1 -1
  38. package/bundled/skills/app-planner/references/rules-configuration.md +158 -88
  39. package/bundled/skills/app-planner/scripts/validate-rules-configuration.py +543 -12
  40. package/bundled/skills/bug-planner/references/verification.md +4 -5
  41. package/bundled/skills/bugfix-pipeline-launcher/SKILL.md +20 -14
  42. package/bundled/skills/bugfix-pipeline-launcher/references/configuration.md +49 -9
  43. package/bundled/skills/feature-pipeline-launcher/SKILL.md +20 -14
  44. package/bundled/skills/feature-pipeline-launcher/references/configuration.md +49 -9
  45. package/bundled/skills/feature-planner/SKILL.md +3 -3
  46. package/bundled/skills/feature-planner/references/browser-interaction.md +9 -29
  47. package/bundled/skills/iterate-pipeline-launcher/SKILL.md +273 -0
  48. package/bundled/skills/iterate-pipeline-launcher/references/configuration.md +105 -0
  49. package/bundled/skills/prizmkit-code-review/SKILL.md +10 -8
  50. package/bundled/skills/prizmkit-code-review/references/independent-code-review.md +4 -1
  51. package/bundled/skills/prizmkit-code-review/references/review-report-template.md +2 -1
  52. package/bundled/skills/prizmkit-code-review/scripts/render_review_report.py +12 -8
  53. package/bundled/skills/prizmkit-implement/SKILL.md +2 -2
  54. package/bundled/skills/prizmkit-init/SKILL.md +10 -10
  55. package/bundled/skills/prizmkit-init/references/brownfield-deep-init.md +81 -0
  56. package/bundled/skills/prizmkit-plan/SKILL.md +2 -1
  57. package/bundled/skills/prizmkit-plan/assets/plan-template.md +2 -0
  58. package/bundled/skills/prizmkit-prizm-docs/SKILL.md +8 -4
  59. package/bundled/skills/prizmkit-prizm-docs/assets/prizm-docs-format.md +8 -7
  60. package/bundled/skills/prizmkit-prizm-docs/references/op-init.md +33 -16
  61. package/bundled/skills/prizmkit-prizm-docs/references/op-validate.md +1 -1
  62. package/bundled/skills/prizmkit-retrospective/SKILL.md +29 -12
  63. package/bundled/skills/prizmkit-retrospective/references/retrospective-result-schema.json +126 -2
  64. package/bundled/skills/prizmkit-retrospective/references/rule-evolution-steps.md +86 -0
  65. package/bundled/skills/prizmkit-test/SKILL.md +2 -1
  66. package/bundled/skills/prizmkit-workflow/SKILL.md +8 -0
  67. package/bundled/skills/prizmkit-workflow/references/cold-start-rules.md +84 -0
  68. package/bundled/templates/project-memory-template.md +3 -3
  69. package/package.json +1 -1
  70. package/src/clean.js +2 -3
  71. package/src/config.js +52 -39
  72. package/src/index.js +29 -111
  73. package/src/prompts.js +20 -87
  74. package/src/runtime-passthrough.js +324 -0
  75. package/src/scaffold.js +41 -294
  76. package/src/upgrade.js +7 -39
  77. package/bundled/dev-pipeline/templates/sections/phase-browser-verification-auto.md +0 -127
  78. package/bundled/dev-pipeline/templates/sections/phase-browser-verification-opencli.md +0 -124
  79. package/src/external-skills.js +0 -103
@@ -1,20 +1,23 @@
1
1
  ---
2
2
  name: "bugfix-pipeline-launcher"
3
- description: "Build bugfix-pipeline commands from a validated .prizmkit/plans/bug-fix-list.json without executing them. Produces foreground or background-daemon start commands plus status, logs, stop, and safe retry commands. Use whenever the user wants to start fixing a prepared bug list, construct a bugfix command, check bugfix status, view logs, stop a run, retry a bug, or clean retry B-001. Trigger on: 'start fixing bugs', 'run bugfix pipeline', 'bugfix status', 'bugfix logs', 'stop bug fix', 'retry bug', 'retry B-001'."
3
+ description: "Build bugfix-pipeline commands from a validated .prizmkit/plans/bug-fix-list.json without executing the pipeline. Supports bounded read-only AI CLI model/effort capability probing on demand and produces foreground or background-daemon start commands plus status, logs, stop, and safe retry commands. Use whenever the user wants to start fixing a prepared bug list, construct a bugfix command, check bugfix status, view logs, stop a run, retry a bug, or clean retry B-001. Trigger on: 'start fixing bugs', 'run bugfix pipeline', 'bugfix status', 'bugfix logs', 'stop bug fix', 'retry bug', 'retry B-001'."
4
4
  ---
5
5
 
6
6
  # Bugfix Pipeline Command Builder
7
7
 
8
- Build commands for the autonomous bugfix pipeline from within an AI CLI conversation. This skill reads configuration and planning inputs, asks only the choices needed to construct an accurate command, displays the command and its effects, then stops.
8
+ Build commands for the autonomous bugfix pipeline from within an AI CLI conversation. This skill reads configuration and planning inputs, runs bounded read-only AI CLI capability probes only when custom model or reasoning effort configuration is needed, asks only the choices required to construct an accurate command, displays the command and its effects, then stops.
9
9
 
10
- ## Command-Only Boundary
10
+ ## Execution Boundary
11
11
 
12
- This skill:
12
+ This skill separates bounded read-only configuration probing from pipeline execution:
13
13
 
14
- - reads a validated bug list and relevant configuration;
15
- - builds prerequisite-check, start, status, logs, stop, and retry commands;
16
- - explains command effects and destructive options before returning them;
17
- - never executes shell commands, starts processes, follows logs, changes pipeline state, fixes source code, or runs verification.
14
+ - **Allowed (bounded read-only configuration probing only)**:
15
+ - read a validated bug list and relevant configuration;
16
+ - build prerequisite-check, start, status, logs, stop, and retry commands;
17
+ - explain command effects and destructive options before returning them;
18
+ - only when the user selects Advanced config or explicitly mentions/asks about a custom model or reasoning effort: run bounded, side-effect-free read-only probes — `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli`, check whether the resolved CLI executable exists on `PATH`, and inspect `<cli> --help` (plus `<cli> exec --help` when applicable). Read-only probes must never invoke prompt runs, interactive logins, file writes, Git mutations, or pipeline state changes.
19
+ - **Prohibited (pipeline execution and state mutation)**:
20
+ - never execute pipeline commands (`run`, `daemon start`, `stop`, `reset`), start processes, follow logs, change pipeline or Git state, fix source code, or run verification unless explicitly requested by the user.
18
21
 
19
22
  Do not invoke another workflow or implementation skill from this command builder. The user decides where and when to run the returned command.
20
23
 
@@ -24,7 +27,7 @@ Use this skill for:
24
27
 
25
28
  - constructing a foreground or background-daemon bugfix pipeline command;
26
29
  - constructing status, logs, stop, or retry commands;
27
- - translating user-selected runtime options into environment variables.
30
+ - translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`, retries, logging) into environment variables.
28
31
 
29
32
  Do not use it to:
30
33
 
@@ -78,7 +81,9 @@ Use a separate `AskUserQuestion` call with exactly three questions:
78
81
  2. **Max retries** — 3, 1, 5, or a user-provided non-negative integer.
79
82
  3. **Advanced config** — No or Yes.
80
83
 
81
- If Advanced config is Yes, load the advanced question set from `${SKILL_DIR}/references/configuration.md`. Advanced configuration contains only stop-on-failure and reasoning effort.
84
+ If Advanced config is No and the user did not specify or ask about a custom model or reasoning effort, skip read-only CLI probing (`diagnostics ai-cli` and `--help`) and record `Read-only CLI probe: skipped (default launch without custom model/effort)`.
85
+
86
+ If Advanced config is Yes — or if the user specified or asked about a custom model or reasoning effort — load `${SKILL_DIR}/references/configuration.md`, run its on-demand read-only CLI capability probe first, and collect confirmed advanced options (stop-on-failure, `MODEL`, and adaptive `PRIZMKIT_EFFORT`) following its four-branch placement rules.
82
87
 
83
88
  ### Step 4: Build command fragments
84
89
 
@@ -90,7 +95,7 @@ Return this prerequisite-check command separately from the pipeline command:
90
95
  python3 ./.prizmkit/dev-pipeline/cli.py diagnostics version && git --version
91
96
  ```
92
97
 
93
- Also include the configured AI CLI check fragment from the reference. These are returned commands, not checks performed by this skill.
98
+ Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even when on-demand read-only probing ran during configuration, pipeline commands are never executed by this skill.
94
99
 
95
100
  ### Step 5: Return the start command
96
101
 
@@ -108,7 +113,7 @@ python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-
108
113
  --env "VERBOSE=1 MAX_RETRIES=3"
109
114
  ```
110
115
 
111
- Return only the template matching the confirmed mode and options. Explain that the command has not been executed, then stop.
116
+ Return only the template matching the confirmed mode and options. Explain that pipeline execution was not performed by this skill, then stop.
112
117
 
113
118
  ## Status Command
114
119
 
@@ -199,6 +204,7 @@ For every request, return:
199
204
  2. Input plan path and selected IDs, when applicable.
200
205
  3. Assumptions and safety warnings.
201
206
  4. Exact command block.
202
- 5. `Command execution: not performed by this skill.`
207
+ 5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (default launch without custom model/effort)>`
208
+ 6. `Pipeline execution: not performed by this skill; run any command above manually when ready.`
203
209
 
204
- Never report command success, process IDs, log locations, bug completion, verification results, or state changes unless the user later supplies authoritative runtime output for explanation.
210
+ Never report pipeline execution success, process IDs, log locations, bug completion, verification results, or state changes unless the user later supplies authoritative runtime output for explanation.
@@ -1,10 +1,10 @@
1
1
  # Configuration Reference — Bugfix Pipeline Command Builder
2
2
 
3
- Use this reference only to translate confirmed user choices into command fragments. The skill returns commands; it does not execute them.
3
+ Use this reference to run bounded on-demand read-only AI CLI capability probing and translate confirmed user choices into command fragments. This skill constructs and returns pipeline commands; it never executes pipeline runs or mutates state unless explicitly requested by the user.
4
4
 
5
5
  ## Configured AI CLI Prerequisite Command
6
6
 
7
- Runtime AI CLI selection is resolved by the canonical runtime across `AI_CLI`, `.prizmkit/config.json` (`ai_cli`), and installed host configuration in the exact order used by `cli.py run`.
7
+ Runtime AI CLI selection is resolved by the canonical runtime across `AI_CLI`, `.prizmkit/config.json` (`ai_cli` and `ai_cli_launch`), `.prizmkit/manifest.json` (`platform`), and installed host configuration in the exact order used by `cli.py run`.
8
8
 
9
9
  Return this cross-platform check command as part of start-command preparation:
10
10
 
@@ -12,7 +12,16 @@ Return this cross-platform check command as part of start-command preparation:
12
12
  python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
13
13
  ```
14
14
 
15
- `diagnostics ai-cli` reports the resolved CLI, source, and runtime mode, and exits non-zero if no configured AI CLI executable is available. Do not claim the configured executable exists until the user supplies successful command output.
15
+ `diagnostics ai-cli` reports `detected_cli`, `platform`, `source`, `runtime_mode`, `model_arg_supported`, `effort_flag_mode`, and `supported_effort_values`, and exits non-zero if no configured AI CLI executable is available.
16
+
17
+ ## On-Demand Read-Only CLI Capability Probe
18
+
19
+ - **Fast default launch (skip probing)**: When Advanced config is not selected and the user did not mention or ask about a custom model or reasoning effort, skip all read-only CLI probing (`diagnostics ai-cli` and `--help`) and output `Read-only CLI probe: skipped (default launch without custom model/effort)`.
20
+ - **On-demand probe trigger**: Run the bounded read-only probe sequence only when Advanced config is selected or the user explicitly specifies or asks about `MODEL` or `PRIZMKIT_EFFORT`:
21
+ 1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` and read the structured capability fields directly: `detected_cli`, `platform`, `source`, `model_arg_supported` (`true`|`false`), `effort_flag_mode` (`flag`|`config`|`none`|`custom_ignored`), and `supported_effort_values` (comma-separated values or `none`). Consume these structured fields directly with zero legacy fallback parsing; if any required capability field is absent, treat the probe as failed under Branch 1.
22
+ 2. If `effort_flag_mode` is `custom_ignored`, route directly to Branch 2 without requiring `<cli> --help`.
23
+ 3. Otherwise, verify that the resolved `detected_cli` executable exists on `PATH` (when not `(not found)`), then run `<cli> --help` (and `<cli> exec --help` when the CLI exposes an `exec` subcommand or `effort_flag_mode` is `config`) to inspect live model flags, independent effort/thinking options, or model-embedded intensity syntax.
24
+ 4. Keep every probe strictly read-only and bounded: never invoke prompt runs, interactive logins, file writes, Git mutations, or pipeline commands (`run`, `daemon start`, `stop`, `reset`). Record a concise summary of observed capability facts in `Read-only CLI probe:`.
16
25
 
17
26
  ## Base Configuration Mapping
18
27
 
@@ -24,21 +33,52 @@ python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
24
33
 
25
34
  ## Advanced Configuration Questions
26
35
 
27
- Ask only when the user selected Advanced config.
36
+ Ask only when the user selected Advanced config or explicitly requested custom model/effort configuration. Configure `MODEL` before `PRIZMKIT_EFFORT`:
28
37
 
29
38
  1. **Stop on failure**
30
39
  - Off (default) — continue to other eligible tasks after a task exhausts retries.
31
40
  - On — add `STOP_ON_FAILURE=1`.
32
- 2. **Reasoning effort**
41
+ 2. **Model (`MODEL`)**
42
+ - Default — omit `MODEL` so the resolved AI CLI uses its default model.
43
+ - Explicit model — add `MODEL=<name>` (or single-quoted `MODEL='<model-with-level>'` for parameterized model syntax) when `model_arg_supported` is `true` (or when probing failed without diagnostics confirming `model_arg_supported: false` and the user explicitly confirms a model name).
44
+ - If `diagnostics ai-cli` reports `effort_flag_mode: custom_ignored`, warn clearly that the active custom launch profile ignores both `MODEL` and `PRIZMKIT_EFFORT` (pass provider flags via `.prizmkit/config.json` `ai_cli_launch.extra_args`). If `model_arg_supported: false` is reported for an unresolved/unsupported profile, warn that `MODEL` is not forwarded and leave it unset.
45
+ - **Per-item precedence**: an individual bug's `"model"` field in `.prizmkit/plans/bug-fix-list.json` takes precedence over the global `MODEL` environment variable during task execution.
46
+ 3. **Reasoning effort (`PRIZMKIT_EFFORT`)**
33
47
  - Default — omit `PRIZMKIT_EFFORT`.
34
- - `low`, `medium`, `high`, `xhigh`, or `max` — add `PRIZMKIT_EFFORT=<value>` after confirming the configured AI CLI supports it.
48
+ - Adaptive placement — determine whether and how to emit `PRIZMKIT_EFFORT` strictly from the four ordered placement branches below (never hardcode one universal effort list or CLI allowlist).
49
+
50
+ ## Adaptive Placement Branches (Evaluate 1 → 4 Strictly in Order)
51
+
52
+ Evaluate branches strictly from 1 to 4 using `diagnostics ai-cli` capability fields plus live `--help` output; the first matching branch governs placement. Never branch on hardcoded platform CLI allowlists.
35
53
 
36
- These are the complete advanced choices for this command builder.
54
+ 1. **Branch 1 — Probe failed, CLI missing, or insufficient help output**:
55
+ - Condition: `diagnostics ai-cli` fails or exits non-zero, `detected_cli` is `(not found)` or missing on `PATH`, required capability fields (`model_arg_supported`, `effort_flag_mode`, `supported_effort_values`) are absent, OR (when `effort_flag_mode` is not `custom_ignored`) `<cli> --help` fails or yields insufficient output.
56
+ - Action: Never guess or synthesize `PRIZMKIT_EFFORT`. Omit `PRIZMKIT_EFFORT`, state the exact probe gap in `Read-only CLI probe:` and warnings, and allow an optional explicit `MODEL=<name>` only if diagnostics did not confirm `model_arg_supported: false` (otherwise leave `MODEL` unset).
57
+ 2. **Branch 2 — Model-embedded intensity syntax or `custom_ignored` profile**:
58
+ - Condition: `effort_flag_mode` is `custom_ignored` (routed directly without letting `<cli> --help` failure trigger Branch 1), OR (`model_arg_supported` is `true`, no compatible independent effort mechanism applies — `effort_flag_mode` is `none`, or `supported_effort_values` is `none`, or `effort_flag_mode` is `flag` with no compatible effort/thinking flag in `--help`, excluding compatible `effort_flag_mode: config` — AND live `--help` documents encoding intensity inside the model identifier syntax such as `<model>:<level>` or parameterized model notation).
59
+ - Action: Omit `PRIZMKIT_EFFORT`. Under `custom_ignored`, warn clearly that the active custom launch profile ignores both `MODEL` and `PRIZMKIT_EFFORT` (configure provider flags via `.prizmkit/config.json` `ai_cli_launch.extra_args`), never emit `PRIZMKIT_EFFORT` (the runtime rejects non-empty `PRIZMKIT_EFFORT` pre-launch on custom profiles), and omit `MODEL` unless the user explicitly overrides. Under model-embedded intensity syntax, guide the user to set `MODEL=<model-with-level>` (or leave `MODEL` unset for the CLI default).
60
+ 3. **Branch 3 — Independent effort explicitly unsupported**:
61
+ - Condition: Branches 1 and 2 do not match, AND `effort_flag_mode` is `none`, OR `supported_effort_values` is `none`, OR `effort_flag_mode` is `flag` yet live `--help` shows no compatible effort/thinking option (excluding compatible `effort_flag_mode: config`).
62
+ - Action: Do not emit `PRIZMKIT_EFFORT` (keep it unset so the runtime does not reject it pre-launch). Still permit `MODEL=<name>` when `model_arg_supported` is `true`.
63
+ 4. **Branch 4 — Independent effort compatible**:
64
+ - Condition: (`effort_flag_mode` is `flag` with live `--help` confirming a compatible effort/thinking option, OR `effort_flag_mode` is `config`) AND `supported_effort_values` is non-empty (not `none`).
65
+ - Action: When live `--help` enumerates concrete effort/thinking values, intersect those enumerated choices with `supported_effort_values`; if the intersection is empty, omit `PRIZMKIT_EFFORT` and disclose the capability mismatch rather than emitting an unvalidated value. Otherwise present the valid choices and emit `PRIZMKIT_EFFORT=<value>` (or omit for default).
37
66
 
38
67
  ## Command Construction Rules
39
68
 
40
- - Foreground: place environment assignments before `python3`.
41
- - Background daemon: place assignments inside one `--env "..."` value.
69
+ - Foreground: place environment assignments (`VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE=...`, `MODEL=...`, `PRIZMKIT_EFFORT=...`) before `python3`.
70
+ - Background daemon: place environment assignments inside one `--env "..."` value.
71
+ - **Parameterized `MODEL` quoting**:
72
+ - Foreground: single-quote parameterized `MODEL` values containing colons, parentheses, spaces, commas, or shell metacharacters:
73
+ ```bash
74
+ MODEL='<model-with-level>' VERBOSE=1 MAX_RETRIES=3 \
75
+ python3 ./.prizmkit/dev-pipeline/cli.py run bugfix .prizmkit/plans/bug-fix-list.json
76
+ ```
77
+ - Background daemon: wrap `--env` in double quotes and single-quote the `MODEL` value inside it so both POSIX and Windows daemon env parsing preserve the full parameter syntax:
78
+ ```bash
79
+ python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json \
80
+ --env "VERBOSE=1 MAX_RETRIES=3 MODEL='<model-with-level>'"
81
+ ```
42
82
  - Include only confirmed options.
43
83
  - Preserve the user-provided list path.
44
84
  - Shell-quote custom paths and values.
@@ -1,20 +1,23 @@
1
1
  ---
2
2
  name: "feature-pipeline-launcher"
3
- description: "Build feature-pipeline commands from a validated .prizmkit/plans/feature-list.json without executing them. Produces foreground or background-daemon start commands plus status, logs, stop, and safe retry commands. Use whenever the user wants to run the feature pipeline, start building from an existing feature list, construct a feature subset command, inspect pipeline status, view logs, stop a run, or retry a feature. Trigger on: 'run pipeline', 'start pipeline', 'start building', 'build feature list', 'pipeline status', 'pipeline logs', 'stop pipeline', 'retry feature', 'clean retry F-001'."
3
+ description: "Build feature-pipeline commands from a validated .prizmkit/plans/feature-list.json without executing the pipeline. Supports bounded read-only AI CLI model/effort capability probing on demand and produces foreground or background-daemon start commands plus status, logs, stop, and safe retry commands. Use whenever the user wants to run the feature pipeline, start building from an existing feature list, construct a feature subset command, inspect pipeline status, view logs, stop a run, or retry a feature. Trigger on: 'run pipeline', 'start pipeline', 'start building', 'build feature list', 'pipeline status', 'pipeline logs', 'stop pipeline', 'retry feature', 'clean retry F-001'."
4
4
  ---
5
5
 
6
6
  # Feature Pipeline Command Builder
7
7
 
8
- Build commands for the autonomous feature pipeline from within an AI CLI conversation. This skill reads configuration and planning inputs, asks only the choices needed to construct an accurate command, displays the command and its effects, then stops.
8
+ Build commands for the autonomous feature pipeline from within an AI CLI conversation. This skill reads configuration and planning inputs, runs bounded read-only AI CLI capability probes only when custom model or reasoning effort configuration is needed, asks only the choices required to construct an accurate command, displays the command and its effects, then stops.
9
9
 
10
- ## Command-Only Boundary
10
+ ## Execution Boundary
11
11
 
12
- This skill:
12
+ This skill separates bounded read-only configuration probing from pipeline execution:
13
13
 
14
- - reads a validated feature list and relevant configuration;
15
- - builds prerequisite-check, start, status, logs, stop, and retry commands;
16
- - explains command effects and destructive options before returning them;
17
- - never executes shell commands, starts processes, follows logs, changes pipeline state, implements source code, or runs verification.
14
+ - **Allowed (bounded read-only configuration probing only)**:
15
+ - read a validated feature list and relevant configuration;
16
+ - build prerequisite-check, start, status, logs, stop, and retry commands;
17
+ - explain command effects and destructive options before returning them;
18
+ - only when the user selects Advanced config or explicitly mentions/asks about a custom model or reasoning effort: run bounded, side-effect-free read-only probes — `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli`, check whether the resolved CLI executable exists on `PATH`, and inspect `<cli> --help` (plus `<cli> exec --help` when applicable). Read-only probes must never invoke prompt runs, interactive logins, file writes, Git mutations, or pipeline state changes.
19
+ - **Prohibited (pipeline execution and state mutation)**:
20
+ - never execute pipeline commands (`run`, `daemon start`, `stop`, `reset`), start processes, follow logs, change pipeline or Git state, implement source code, or run verification unless explicitly requested by the user.
18
21
 
19
22
  Do not invoke another workflow or implementation skill from this command builder. The user decides where and when to run the returned command.
20
23
 
@@ -25,7 +28,7 @@ Use this skill for:
25
28
  - constructing a foreground or background-daemon feature pipeline command;
26
29
  - selecting a feature subset such as `F-001:F-005` or `F-001,F-003`;
27
30
  - constructing status, logs, stop, or retry commands;
28
- - translating user-selected runtime options into environment variables.
31
+ - translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`, retries, logging) into environment variables.
29
32
 
30
33
  Do not use it to:
31
34
 
@@ -82,7 +85,9 @@ Use a separate `AskUserQuestion` call with exactly three questions:
82
85
  2. **Max retries** — 3, 1, 5, or a user-provided non-negative integer.
83
86
  3. **Advanced config** — No or Yes.
84
87
 
85
- If Advanced config is Yes, load the advanced question set from `${SKILL_DIR}/references/configuration.md`. Advanced configuration contains only stop-on-failure and reasoning effort.
88
+ If Advanced config is No and the user did not specify or ask about a custom model or reasoning effort, skip read-only CLI probing (`diagnostics ai-cli` and `--help`) and record `Read-only CLI probe: skipped (default launch without custom model/effort)`.
89
+
90
+ If Advanced config is Yes — or if the user specified or asked about a custom model or reasoning effort — load `${SKILL_DIR}/references/configuration.md`, run its on-demand read-only CLI capability probe first, and collect confirmed advanced options (stop-on-failure, `MODEL`, and adaptive `PRIZMKIT_EFFORT`) following its four-branch placement rules.
86
91
 
87
92
  ### Step 4: Build command fragments
88
93
 
@@ -94,7 +99,7 @@ Build the prerequisite-check command separately from the pipeline command so the
94
99
  python3 ./.prizmkit/dev-pipeline/cli.py diagnostics version && git --version
95
100
  ```
96
101
 
97
- Also include the configured AI CLI check fragment from the reference. These are returned commands, not checks performed by this skill.
102
+ Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even when on-demand read-only probing ran during configuration, pipeline commands are never executed by this skill.
98
103
 
99
104
  ### Step 5: Return the start command
100
105
 
@@ -126,7 +131,7 @@ python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/fea
126
131
  --features F-001:F-005 --env "VERBOSE=1 MAX_RETRIES=3"
127
132
  ```
128
133
 
129
- Return only the template matching the confirmed mode and options. Explain that the command has not been executed, then stop.
134
+ Return only the template matching the confirmed mode and options. Explain that pipeline execution was not performed by this skill, then stop.
130
135
 
131
136
  ## Status Command
132
137
 
@@ -217,6 +222,7 @@ For every request, return:
217
222
  2. Input plan path and selected IDs, when applicable.
218
223
  3. Assumptions and safety warnings.
219
224
  4. Exact command block.
220
- 5. `Command execution: not performed by this skill.`
225
+ 5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (default launch without custom model/effort)>`
226
+ 6. `Pipeline execution: not performed by this skill; run any command above manually when ready.`
221
227
 
222
- Never report command success, process IDs, log locations, task completion, verification results, or state changes unless the user later supplies authoritative runtime output for explanation.
228
+ Never report pipeline execution success, process IDs, log locations, task completion, verification results, or state changes unless the user later supplies authoritative runtime output for explanation.
@@ -1,10 +1,10 @@
1
1
  # Configuration Reference — Feature Pipeline Command Builder
2
2
 
3
- Use this reference only to translate confirmed user choices into command fragments. The skill returns commands; it does not execute them.
3
+ Use this reference to run bounded on-demand read-only AI CLI capability probing and translate confirmed user choices into command fragments. This skill constructs and returns pipeline commands; it never executes pipeline runs or mutates state unless explicitly requested by the user.
4
4
 
5
5
  ## Configured AI CLI Prerequisite Command
6
6
 
7
- Runtime AI CLI selection is resolved by the canonical runtime across `AI_CLI`, `.prizmkit/config.json` (`ai_cli`), and installed host configuration in the exact order used by `cli.py run`.
7
+ Runtime AI CLI selection is resolved by the canonical runtime across `AI_CLI`, `.prizmkit/config.json` (`ai_cli` and `ai_cli_launch`), `.prizmkit/manifest.json` (`platform`), and installed host configuration in the exact order used by `cli.py run`.
8
8
 
9
9
  Return this cross-platform check command as part of start-command preparation:
10
10
 
@@ -12,7 +12,16 @@ Return this cross-platform check command as part of start-command preparation:
12
12
  python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
13
13
  ```
14
14
 
15
- `diagnostics ai-cli` reports the resolved CLI, source, and runtime mode, and exits non-zero if no configured AI CLI executable is available. Do not claim the configured executable exists until the user supplies successful command output.
15
+ `diagnostics ai-cli` reports `detected_cli`, `platform`, `source`, `runtime_mode`, `model_arg_supported`, `effort_flag_mode`, and `supported_effort_values`, and exits non-zero if no configured AI CLI executable is available.
16
+
17
+ ## On-Demand Read-Only CLI Capability Probe
18
+
19
+ - **Fast default launch (skip probing)**: When Advanced config is not selected and the user did not mention or ask about a custom model or reasoning effort, skip all read-only CLI probing (`diagnostics ai-cli` and `--help`) and output `Read-only CLI probe: skipped (default launch without custom model/effort)`.
20
+ - **On-demand probe trigger**: Run the bounded read-only probe sequence only when Advanced config is selected or the user explicitly specifies or asks about `MODEL` or `PRIZMKIT_EFFORT`:
21
+ 1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` and read the structured capability fields directly: `detected_cli`, `platform`, `source`, `model_arg_supported` (`true`|`false`), `effort_flag_mode` (`flag`|`config`|`none`|`custom_ignored`), and `supported_effort_values` (comma-separated values or `none`). Consume these structured fields directly with zero legacy fallback parsing; if any required capability field is absent, treat the probe as failed under Branch 1.
22
+ 2. If `effort_flag_mode` is `custom_ignored`, route directly to Branch 2 without requiring `<cli> --help`.
23
+ 3. Otherwise, verify that the resolved `detected_cli` executable exists on `PATH` (when not `(not found)`), then run `<cli> --help` (and `<cli> exec --help` when the CLI exposes an `exec` subcommand or `effort_flag_mode` is `config`) to inspect live model flags, independent effort/thinking options, or model-embedded intensity syntax.
24
+ 4. Keep every probe strictly read-only and bounded: never invoke prompt runs, interactive logins, file writes, Git mutations, or pipeline commands (`run`, `daemon start`, `stop`, `reset`). Record a concise summary of observed capability facts in `Read-only CLI probe:`.
16
25
 
17
26
  ## Base Configuration Mapping
18
27
 
@@ -24,21 +33,52 @@ python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
24
33
 
25
34
  ## Advanced Configuration Questions
26
35
 
27
- Ask only when the user selected Advanced config.
36
+ Ask only when the user selected Advanced config or explicitly requested custom model/effort configuration. Configure `MODEL` before `PRIZMKIT_EFFORT`:
28
37
 
29
38
  1. **Stop on failure**
30
39
  - Off (default) — continue to other eligible tasks after a task exhausts retries.
31
40
  - On — add `STOP_ON_FAILURE=1`.
32
- 2. **Reasoning effort**
41
+ 2. **Model (`MODEL`)**
42
+ - Default — omit `MODEL` so the resolved AI CLI uses its default model.
43
+ - Explicit model — add `MODEL=<name>` (or single-quoted `MODEL='<model-with-level>'` for parameterized model syntax) when `model_arg_supported` is `true` (or when probing failed without diagnostics confirming `model_arg_supported: false` and the user explicitly confirms a model name).
44
+ - If `diagnostics ai-cli` reports `effort_flag_mode: custom_ignored`, warn clearly that the active custom launch profile ignores both `MODEL` and `PRIZMKIT_EFFORT` (pass provider flags via `.prizmkit/config.json` `ai_cli_launch.extra_args`). If `model_arg_supported: false` is reported for an unresolved/unsupported profile, warn that `MODEL` is not forwarded and leave it unset.
45
+ - **Per-item precedence**: an individual feature's `"model"` field in `.prizmkit/plans/feature-list.json` takes precedence over the global `MODEL` environment variable during task execution.
46
+ 3. **Reasoning effort (`PRIZMKIT_EFFORT`)**
33
47
  - Default — omit `PRIZMKIT_EFFORT`.
34
- - `low`, `medium`, `high`, `xhigh`, or `max` — add `PRIZMKIT_EFFORT=<value>` after confirming the configured AI CLI supports it.
48
+ - Adaptive placement — determine whether and how to emit `PRIZMKIT_EFFORT` strictly from the four ordered placement branches below (never hardcode one universal effort list or CLI allowlist).
49
+
50
+ ## Adaptive Placement Branches (Evaluate 1 → 4 Strictly in Order)
51
+
52
+ Evaluate branches strictly from 1 to 4 using `diagnostics ai-cli` capability fields plus live `--help` output; the first matching branch governs placement. Never branch on hardcoded platform CLI allowlists.
35
53
 
36
- These are the complete advanced choices for this command builder.
54
+ 1. **Branch 1 — Probe failed, CLI missing, or insufficient help output**:
55
+ - Condition: `diagnostics ai-cli` fails or exits non-zero, `detected_cli` is `(not found)` or missing on `PATH`, required capability fields (`model_arg_supported`, `effort_flag_mode`, `supported_effort_values`) are absent, OR (when `effort_flag_mode` is not `custom_ignored`) `<cli> --help` fails or yields insufficient output.
56
+ - Action: Never guess or synthesize `PRIZMKIT_EFFORT`. Omit `PRIZMKIT_EFFORT`, state the exact probe gap in `Read-only CLI probe:` and warnings, and allow an optional explicit `MODEL=<name>` only if diagnostics did not confirm `model_arg_supported: false` (otherwise leave `MODEL` unset).
57
+ 2. **Branch 2 — Model-embedded intensity syntax or `custom_ignored` profile**:
58
+ - Condition: `effort_flag_mode` is `custom_ignored` (routed directly without letting `<cli> --help` failure trigger Branch 1), OR (`model_arg_supported` is `true`, no compatible independent effort mechanism applies — `effort_flag_mode` is `none`, or `supported_effort_values` is `none`, or `effort_flag_mode` is `flag` with no compatible effort/thinking flag in `--help`, excluding compatible `effort_flag_mode: config` — AND live `--help` documents encoding intensity inside the model identifier syntax such as `<model>:<level>` or parameterized model notation).
59
+ - Action: Omit `PRIZMKIT_EFFORT`. Under `custom_ignored`, warn clearly that the active custom launch profile ignores both `MODEL` and `PRIZMKIT_EFFORT` (configure provider flags via `.prizmkit/config.json` `ai_cli_launch.extra_args`), never emit `PRIZMKIT_EFFORT` (the runtime rejects non-empty `PRIZMKIT_EFFORT` pre-launch on custom profiles), and omit `MODEL` unless the user explicitly overrides. Under model-embedded intensity syntax, guide the user to set `MODEL=<model-with-level>` (or leave `MODEL` unset for the CLI default).
60
+ 3. **Branch 3 — Independent effort explicitly unsupported**:
61
+ - Condition: Branches 1 and 2 do not match, AND `effort_flag_mode` is `none`, OR `supported_effort_values` is `none`, OR `effort_flag_mode` is `flag` yet live `--help` shows no compatible effort/thinking option (excluding compatible `effort_flag_mode: config`).
62
+ - Action: Do not emit `PRIZMKIT_EFFORT` (keep it unset so the runtime does not reject it pre-launch). Still permit `MODEL=<name>` when `model_arg_supported` is `true`.
63
+ 4. **Branch 4 — Independent effort compatible**:
64
+ - Condition: (`effort_flag_mode` is `flag` with live `--help` confirming a compatible effort/thinking option, OR `effort_flag_mode` is `config`) AND `supported_effort_values` is non-empty (not `none`).
65
+ - Action: When live `--help` enumerates concrete effort/thinking values, intersect those enumerated choices with `supported_effort_values`; if the intersection is empty, omit `PRIZMKIT_EFFORT` and disclose the capability mismatch rather than emitting an unvalidated value. Otherwise present the valid choices and emit `PRIZMKIT_EFFORT=<value>` (or omit for default).
37
66
 
38
67
  ## Command Construction Rules
39
68
 
40
- - Foreground: place environment assignments before `python3`.
41
- - Background daemon: place assignments inside one `--env "..."` value.
69
+ - Foreground: place environment assignments (`VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE=...`, `MODEL=...`, `PRIZMKIT_EFFORT=...`) before `python3`.
70
+ - Background daemon: place environment assignments inside one `--env "..."` value.
71
+ - **Parameterized `MODEL` quoting**:
72
+ - Foreground: single-quote parameterized `MODEL` values containing colons, parentheses, spaces, commas, or shell metacharacters:
73
+ ```bash
74
+ MODEL='<model-with-level>' VERBOSE=1 MAX_RETRIES=3 \
75
+ python3 ./.prizmkit/dev-pipeline/cli.py run feature .prizmkit/plans/feature-list.json
76
+ ```
77
+ - Background daemon: wrap `--env` in double quotes and single-quote the `MODEL` value inside it so both POSIX and Windows daemon env parsing preserve the full parameter syntax:
78
+ ```bash
79
+ python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json \
80
+ --env "VERBOSE=1 MAX_RETRIES=3 MODEL='<model-with-level>'"
81
+ ```
42
82
  - Include only confirmed options.
43
83
  - Preserve the user-provided list path and feature filter.
44
84
  - Shell-quote custom paths and values.
@@ -87,9 +87,9 @@ Eligible only when ALL apply: incremental mode, `1-2` features max, each `<=5` c
87
87
 
88
88
  ## Browser Interaction Planning
89
89
 
90
- Qualifying features (`global_context.frontend_framework` present + UI criteria, excluding backend/config/`completed`) receive `browser_interaction` by default:
91
- 1. **Ask user for browser tool preference (Mandatory)** via `AskUserQuestion` using `${SKILL_DIR}/references/browser-interaction.md` §Browser Tool Selection (`auto` / `playwright-cli` / `opencli`) before generating fields.
92
- 2. Auto-generate `browser_interaction` (`opencli` for OAuth/SSO/login state, `playwright-cli` for local UI), show a batch summary (allow per-feature opt-out/override), and follow `${SKILL_DIR}/references/browser-interaction.md` field rules.
90
+ Qualifying features (`global_context.frontend_framework` present + UI criteria, excluding backend/config/`completed`) receive `browser_interaction` with `tool: "playwright-cli"` by default:
91
+ 1. Auto-generate `browser_interaction` (`tool: "playwright-cli"`, `verify_steps`) for all qualifying features following `${SKILL_DIR}/references/browser-interaction.md` field rules.
92
+ 2. Show a batch summary of which features received `browser_interaction` and allow per-feature opt-out or `verify_steps`/`blocking` override without prompting for browser tool selection.
93
93
 
94
94
  ## Output Rules & Local Generated-Plan Review Gate
95
95
 
@@ -1,28 +1,19 @@
1
1
  # Browser Interaction Planning
2
2
 
3
- For web apps with UI, features that involve user-facing pages or interactive flows can optionally include a `browser_interaction` field. This enables the dev-pipeline to verify UI behavior automatically after implementation using the configured browser tool (`playwright-cli` or `opencli`).
4
-
5
- ## Browser Tool Selection (Mandatory — Ask User)
6
-
7
- Before auto-generating `browser_interaction` for features, you MUST ask the user which browser tool to use as the project default via `AskUserQuestion`:
8
-
9
- **Question**: "Which browser verification tool should this project use by default?"
10
- - **Auto — AI chooses per feature (Recommended)** — `playwright-cli` for local UI, `opencli` for authenticated flows. AI decides per-feature at planning time.
11
- - **playwright-cli** — isolated browser instance, no login state. Best for local dev server, forms, components.
12
- - **opencli** — reuses Chrome's logged-in sessions via Browser Bridge. Best for OAuth, third-party dashboards, SSO.
13
-
14
- Store the user's choice as the project-level default. Individual features can still override (see Tool Selection per Feature below).
3
+ For web apps with UI, features that involve user-facing pages or interactive flows receive a `browser_interaction` field by default. This enables the dev-pipeline to verify UI behavior automatically after implementation using `playwright-cli`.
15
4
 
16
5
  ## How to Capture
17
6
 
18
- During Phase 4.2, auto-generate `browser_interaction` for all qualifying features (see SKILL.md §Browser Interaction Planning for auto-detection rules). Present a **batch summary** to the user showing which features received `browser_interaction` — do NOT ask per-feature. The user can opt out specific features from the summary.
7
+ During Phase 4.2, auto-generate `browser_interaction` with `tool: "playwright-cli"` for all qualifying features (see `SKILL.md` §Browser Interaction Planning for auto-detection rules) — do NOT prompt for browser tool selection or ask per feature.
8
+
9
+ Present a **batch summary** to the user showing which features received `browser_interaction`. In that summary, the user can opt out specific features or override `verify_steps` / `blocking` per item.
19
10
 
20
11
  For each qualifying feature, generate the `browser_interaction` object:
21
12
 
22
13
  ```json
23
14
  {
24
15
  "browser_interaction": {
25
- "tool": "auto",
16
+ "tool": "playwright-cli",
26
17
  "verify_steps": [
27
18
  "Verify login form renders with email and password fields",
28
19
  "Verify valid credentials redirect to dashboard",
@@ -34,19 +25,8 @@ For each qualifying feature, generate the `browser_interaction` object:
34
25
 
35
26
  ## Field Rules
36
27
 
37
- - `tool` selects the browser verification tool. Values: `"playwright-cli"`, `"opencli"`, `"auto"` (default).
38
- - **`"auto"`** (default): AI chooses at runtime based on available tools and scenario. Recommended for most cases.
39
- - **`"playwright-cli"`**: Isolated browser instance, no login state. Best for local dev server verification, form testing, component rendering checks.
40
- - **`"opencli"`**: Reuses Chrome's logged-in sessions via Browser Bridge. Best for verifying third-party integrations (OAuth callbacks, API dashboards), features requiring real authentication state, or pages behind SSO.
41
-
42
- | Scenario | Recommended `tool` |
43
- |----------|-------------------|
44
- | Local dev server, pure frontend components | `playwright-cli` |
45
- | Needs real login state (e.g., OAuth redirect page) | `opencli` |
46
- | Third-party API integration dashboard verification | `opencli` |
47
- | Headless CI environment | `playwright-cli` |
48
- | Unsure / mixed scenarios | `auto` |
49
-
28
+ - `tool`: Always `"playwright-cli"` (the default and sole supported browser verification tool, using an isolated local browser against the project's dev server).
29
+ - `blocking`: Optional boolean (defaults to `false` when omitted). Set to `true` only when a browser verification failure must block commit.
50
30
  - `verify_steps` are **verification goals**, not specific tool commands. Describe WHAT to verify, not HOW to verify it. The pipeline AI will:
51
31
  1. Auto-detect the dev server start command from project config (`package.json`, `Makefile`, etc.)
52
32
  2. Start the server and discover the URL/port at runtime
@@ -55,5 +35,5 @@ For each qualifying feature, generate the `browser_interaction` object:
55
35
  This works better than prescribing URLs/commands at planning time because: (1) ports may differ across environments, (2) element refs don't exist yet, (3) UI structure may change during implementation, (4) the AI has full context of the actual code when it runs verification.
56
36
  - **Good**: `"Verify login form accepts valid credentials and redirects to dashboard"`
57
37
  - **Bad**: `"click <ref> — click login button"` (guesses at refs that don't exist yet)
58
- - Do NOT specify `url`, `setup_command`, or `port` — the AI detects these at runtime from the actual project configuration
59
- - An empty `browser_interaction: {}` object (no verify_steps) is valid — the AI will explore the app and verify the feature works as expected
38
+ - Do NOT specify `url`, `setup_command`, or `port` — the AI detects these at runtime from the actual project configuration.
39
+ - An empty `browser_interaction: {}` object (no `verify_steps`) is valid — it defaults to `tool: "playwright-cli"` and the AI explores the app to verify the feature works as expected.