prizmkit 1.1.196 → 1.1.198
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.
- package/bin/create-prizmkit.js +1 -7
- package/bundled/VERSION.json +3 -3
- package/bundled/adapters/antigravity/assets/prizmkit-hook.cjs +1 -1
- package/bundled/adapters/antigravity/rules-adapter.js +1 -13
- package/bundled/adapters/claude/paths.js +0 -1
- package/bundled/adapters/claude/settings-adapter.js +3 -8
- package/bundled/adapters/codex/paths.js +0 -1
- package/bundled/adapters/codex/settings-adapter.js +1 -1
- package/bundled/adapters/cursor/assets/prizmkit-hook.cjs +1 -1
- package/bundled/adapters/cursor/rules-adapter.js +1 -13
- package/bundled/adapters/pi/paths.js +0 -1
- package/bundled/dev-pipeline/.env.example +2 -2
- package/bundled/dev-pipeline/README.md +6 -5
- package/bundled/dev-pipeline/assets/skill-subagent-integration.md +2 -2
- package/bundled/dev-pipeline/prizmkit_runtime/checkpoint_state.py +15 -25
- package/bundled/dev-pipeline/prizmkit_runtime/iterate.py +1 -69
- package/bundled/dev-pipeline/prizmkit_runtime/platform_detection.py +1 -114
- package/bundled/dev-pipeline/prizmkit_runtime/runner_models.py +2 -2
- package/bundled/dev-pipeline/prizmkit_runtime/runners.py +78 -0
- package/bundled/dev-pipeline/prizmkit_runtime/runtime_helper.py +4 -234
- package/bundled/dev-pipeline/prizmkit_runtime/status.py +0 -5
- package/bundled/dev-pipeline/prizmkit_runtime/stream_progress.py +9 -1
- package/bundled/dev-pipeline/scripts/feature_list_contract.py +0 -43
- package/bundled/dev-pipeline/scripts/generate-bootstrap-prompt.py +15 -76
- package/bundled/dev-pipeline/scripts/generate-bugfix-prompt.py +9 -112
- package/bundled/dev-pipeline/scripts/init-bugfix-pipeline.py +0 -13
- package/bundled/dev-pipeline/scripts/init-pipeline.py +0 -1
- package/bundled/dev-pipeline/scripts/prompt_framework.py +0 -79
- package/bundled/dev-pipeline/scripts/status_common.py +150 -4
- package/bundled/dev-pipeline/scripts/update-bug-status.py +20 -2
- package/bundled/dev-pipeline/scripts/update-feature-status.py +20 -2
- package/bundled/dev-pipeline/scripts/utils.py +6 -0
- package/bundled/dev-pipeline/templates/bootstrap-prompt.md +4 -5
- package/bundled/dev-pipeline/templates/bootstrap-tier3.md +5 -101
- package/bundled/dev-pipeline/templates/bug-fix-list-schema.json +0 -35
- package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md +4 -52
- package/bundled/dev-pipeline/templates/feature-list-schema.json +0 -25
- package/bundled/dev-pipeline/templates/iterate/evaluate-prompt.md +5 -16
- package/bundled/dev-pipeline/templates/iterate/evaluation-schema.json +1 -58
- package/bundled/dev-pipeline/templates/iterate/headless-plan-prompt.md +1 -12
- package/bundled/dev-pipeline/templates/sections/artifact-manifest.md +0 -1
- package/bundled/dev-pipeline/templates/sections/bugfix-phase-commit-report.md +0 -1
- package/bundled/dev-pipeline/templates/sections/bugfix-phase-diagnose-plan.md +2 -2
- package/bundled/dev-pipeline/templates/sections/bugfix-phase-review.md +1 -1
- package/bundled/dev-pipeline/templates/sections/bugfix-phase-test.md +1 -1
- package/bundled/dev-pipeline/templates/sections/bugfix-reminders.md +0 -2
- package/bundled/dev-pipeline/templates/sections/bugfix-session-context.md +0 -1
- package/bundled/dev-pipeline/templates/sections/bugfix-task-contract.md +0 -5
- package/bundled/dev-pipeline/templates/sections/checkpoint-system.md +1 -2
- package/bundled/dev-pipeline/templates/sections/feature-completion-summary.md +1 -1
- package/bundled/dev-pipeline/templates/sections/phase-commit-full.md +3 -3
- package/bundled/dev-pipeline/templates/sections/phase-prizmkit-test.md +3 -3
- package/bundled/dev-pipeline/templates/sections/phase-review-full.md +3 -3
- package/bundled/dev-pipeline/templates/sections/phase-specify-plan-full.md +1 -1
- package/bundled/dev-pipeline/templates/sections/retrospective.md +3 -3
- package/bundled/dev-pipeline/templates/sections/runtime-commit-handoff.md +1 -1
- package/bundled/rules/USAGE.md +5 -19
- package/bundled/rules/general/coding-baseline.md +2 -2
- package/bundled/rules/prizm/prizm-progressive-loading.md +2 -1
- package/bundled/skills/_metadata.json +4 -4
- package/bundled/skills/app-planner/SKILL.md +1 -1
- package/bundled/skills/app-planner/references/generated-plan-review.md +1 -1
- package/bundled/skills/app-planner/references/rules-configuration.md +6 -7
- package/bundled/skills/app-planner/scripts/validate-rules-configuration.py +2 -20
- package/bundled/skills/bug-planner/SKILL.md +5 -6
- package/bundled/skills/bug-planner/assets/bug-confirmation-template.md +1 -1
- package/bundled/skills/bug-planner/references/input-formats.md +2 -2
- package/bundled/skills/bug-planner/references/schema-validation.md +0 -1
- package/bundled/skills/bug-planner/scripts/validate-bug-list.py +2 -9
- package/bundled/skills/bugfix-pipeline-launcher/SKILL.md +36 -25
- package/bundled/skills/bugfix-pipeline-launcher/references/configuration.md +32 -26
- package/bundled/skills/feature-pipeline-launcher/SKILL.md +33 -25
- package/bundled/skills/feature-pipeline-launcher/references/configuration.md +32 -26
- package/bundled/skills/feature-planner/SKILL.md +4 -10
- package/bundled/skills/feature-planner/references/completeness-review.md +2 -2
- package/bundled/skills/feature-planner/references/new-project-planning.md +0 -1
- package/bundled/skills/feature-planner/scripts/validate-and-generate.py +1 -25
- package/bundled/skills/iterate-pipeline-launcher/SKILL.md +53 -42
- package/bundled/skills/iterate-pipeline-launcher/references/configuration.md +47 -43
- package/bundled/skills/prizmkit-code-review/SKILL.md +1 -1
- package/bundled/skills/prizmkit-code-review/references/independent-code-review.md +2 -2
- package/bundled/skills/prizmkit-implement/SKILL.md +1 -1
- package/bundled/skills/prizmkit-init/SKILL.md +6 -7
- package/bundled/skills/prizmkit-init/references/config-schema.md +5 -9
- package/bundled/skills/prizmkit-init/references/rules/layer-detection.md +1 -1
- package/bundled/skills/prizmkit-plan/SKILL.md +1 -1
- package/bundled/skills/prizmkit-retrospective/SKILL.md +3 -3
- package/bundled/skills/prizmkit-retrospective/references/rule-evolution-steps.md +11 -17
- package/bundled/skills/prizmkit-workflow/SKILL.md +6 -3
- package/bundled/skills/prizmkit-workflow/references/cold-start-rules.md +8 -7
- package/bundled/templates/project-memory-template.md +2 -1
- package/package.json +1 -1
- package/src/clean.js +29 -7
- package/src/config.js +29 -48
- package/src/index.js +2 -9
- package/src/manifest.js +5 -9
- package/src/platforms.js +0 -14
- package/src/prompts.js +0 -13
- package/src/scaffold.js +100 -327
- package/src/upgrade.js +38 -42
- package/bundled/adapters/claude/rules-adapter.js +0 -25
- package/bundled/adapters/codebuddy/rules-adapter.js +0 -30
- package/bundled/adapters/codex/rules-adapter.js +0 -30
- package/bundled/adapters/pi/rules-adapter.js +0 -13
- package/bundled/dev-pipeline/templates/sections/bugfix-phase-manual-verification.md +0 -10
- package/bundled/dev-pipeline/templates/sections/phase-browser-verification.md +0 -111
- package/bundled/skills/bug-planner/references/verification.md +0 -26
- package/bundled/skills/feature-planner/references/browser-interaction.md +0 -39
|
@@ -1,11 +1,11 @@
|
|
|
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 the pipeline.
|
|
3
|
+
description: "Build bugfix-pipeline commands from a validated .prizmkit/plans/bug-fix-list.json without executing the pipeline. Runs start-time bounded read-only AI CLI model/effort capability probing (skipped on non-start intents) 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.
|
|
8
|
+
Build commands for the autonomous bugfix pipeline from within an AI CLI conversation. On start intents, this skill reads planning inputs, runs bounded start-time read-only AI CLI capability probing after execution-mode selection, displays a Default Parameters Overview Table, asks one focused configuration round (`MODEL`, conditional `PRIZMKIT_EFFORT`, and whether to customize other defaults), displays the command and its effects, then stops. Non-start intents skip CLI probing.
|
|
9
9
|
|
|
10
10
|
## Execution Boundary
|
|
11
11
|
|
|
@@ -15,7 +15,7 @@ This skill separates bounded read-only configuration probing from pipeline execu
|
|
|
15
15
|
- read a validated bug list and relevant configuration;
|
|
16
16
|
- build prerequisite-check, start, status, logs, stop, and retry commands;
|
|
17
17
|
- explain command effects and destructive options before returning them;
|
|
18
|
-
-
|
|
18
|
+
- on every Start intent (after Step 2 execution-mode selection): run bounded, side-effect-free read-only probes — `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` (or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` when a temporary `AI_CLI=<cli>` override is given), route `effort_flag_mode: custom_ignored` directly to Branch 2, otherwise verify `cli_available: true` and executable availability 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. Non-start intents (`status`, `logs`, `stop`, `retry`) skip read-only probing and record `Read-only CLI probe: skipped (non-start intent)`.
|
|
19
19
|
- **Prohibited (pipeline execution and state mutation)**:
|
|
20
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.
|
|
21
21
|
|
|
@@ -27,7 +27,7 @@ Use this skill for:
|
|
|
27
27
|
|
|
28
28
|
- constructing a foreground or background-daemon bugfix pipeline command;
|
|
29
29
|
- constructing status, logs, stop, or retry commands;
|
|
30
|
-
- translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`,
|
|
30
|
+
- translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`, and optional default overrides) into environment variables.
|
|
31
31
|
|
|
32
32
|
Do not use it to:
|
|
33
33
|
|
|
@@ -46,15 +46,17 @@ Accept a user-specified bug-list path when provided. Read the plan directly to s
|
|
|
46
46
|
|
|
47
47
|
## Intent Routing
|
|
48
48
|
|
|
49
|
+
Classify the request before asking configuration questions:
|
|
50
|
+
|
|
49
51
|
| Intent | Output |
|
|
50
52
|
|---|---|
|
|
51
|
-
| Start prepared bugs | Prerequisite-check command plus one start command |
|
|
52
|
-
| Check status | Daemon status and item-level status commands |
|
|
53
|
-
| Show logs | Recent or follow-log command |
|
|
54
|
-
| Stop | Daemon stop command plus optional status command |
|
|
55
|
-
| Retry failed bug work | State-only, preserve-runtime, fresh-checkout, or clean reset plus a separate run command with safety disclosure |
|
|
53
|
+
| Start prepared bugs | Prerequisite-check command plus one start command (runs start-time read-only CLI probe) |
|
|
54
|
+
| Check status | Daemon status and item-level status commands (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
55
|
+
| Show logs | Recent or follow-log command (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
56
|
+
| Stop | Daemon stop command plus optional status command (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
57
|
+
| Retry failed bug work | State-only, preserve-runtime, fresh-checkout, or clean reset plus a separate run command with safety disclosure (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
56
58
|
|
|
57
|
-
Only the start intent uses the execution-mode and configuration rounds.
|
|
59
|
+
Only the start intent uses the execution-mode, start-time CLI probe, and configuration rounds. Non-start intents (`status`, `logs`, `stop`, `retry`) skip probing and emit `Read-only CLI probe: skipped (non-start intent)`.
|
|
58
60
|
|
|
59
61
|
## Start Command Workflow
|
|
60
62
|
|
|
@@ -62,7 +64,8 @@ Only the start intent uses the execution-mode and configuration rounds.
|
|
|
62
64
|
|
|
63
65
|
1. Resolve the bug-list path.
|
|
64
66
|
2. Read the list and summarize total, eligible, blocked, and selected bug IDs.
|
|
65
|
-
3.
|
|
67
|
+
3. Preserve any temporary `AI_CLI=<cli>` override directly; carry it forward into the Default Parameters Overview Table and final command without re-asking.
|
|
68
|
+
4. If an existing run is suspected from user context, include a status command in the output; do not run it.
|
|
66
69
|
|
|
67
70
|
### Step 2: Ask execution mode
|
|
68
71
|
|
|
@@ -71,23 +74,31 @@ Use one `AskUserQuestion` call with exactly one question:
|
|
|
71
74
|
- **Foreground (Recommended)** — build `run bugfix`; output remains attached to the user's terminal.
|
|
72
75
|
- **Background daemon** — build `daemon bugfix start`; the runtime manages detached execution and logs.
|
|
73
76
|
|
|
74
|
-
Wait for the response before
|
|
75
|
-
|
|
76
|
-
### Step 3: Ask base configuration
|
|
77
|
+
Wait for the response before Step 3.
|
|
77
78
|
|
|
78
|
-
|
|
79
|
+
### Step 3: Probe CLI capabilities, show default parameters, and ask focused configuration
|
|
79
80
|
|
|
80
|
-
1.
|
|
81
|
-
2. **
|
|
82
|
-
3. **Advanced config** — No or Yes.
|
|
81
|
+
1. Load `${SKILL_DIR}/references/configuration.md` and run its start-time bounded read-only AI CLI capability probe sequence first: execute `diagnostics ai-cli` (honoring any temporary `AI_CLI=<cli>` override), consume structured capability fields directly with zero legacy fallback parsing, route `effort_flag_mode: custom_ignored` directly to Branch 2 without letting `<cli> --help` trigger Branch 1, otherwise verify `cli_available: true` and executable availability on `PATH`, and inspect `<cli> --help` (plus `<cli> exec --help` when applicable).
|
|
82
|
+
2. Display the **Default Parameters Overview Table** before asking configuration questions (noting any pre-specified `AI_CLI` value as already specified):
|
|
83
83
|
|
|
84
|
-
|
|
84
|
+
| Parameter | Default | Meaning |
|
|
85
|
+
|---|---|---|
|
|
86
|
+
| `VERBOSE` | `1` | Enable verbose runtime session logging |
|
|
87
|
+
| `MAX_RETRIES` | `3` | Maximum retry attempts per task before marking failed |
|
|
88
|
+
| `STOP_ON_FAILURE` | `1` | Stop subsequent pipeline execution immediately when a task fails (runtime default; override with `STOP_ON_FAILURE=0` to continue to other eligible tasks) |
|
|
85
89
|
|
|
86
|
-
|
|
90
|
+
3. Then use a separate `AskUserQuestion` call covering only:
|
|
91
|
+
- **`MODEL`** — Default (omit `MODEL` to use the CLI default) or explicit/parameterized model name guided by probe evidence. Under `effort_flag_mode: custom_ignored` or `model_arg_supported: false`, warn clearly per the reference and leave `MODEL` unset. Remember that an individual bug's `"model"` field in `.prizmkit/plans/bug-fix-list.json` takes precedence over global `MODEL`.
|
|
92
|
+
- **`PRIZMKIT_EFFORT`** *(conditional — Branch 4 only)* — ask **only** when Branch 4 of the four ordered adaptive placement branches matches with a non-empty intersection of live `--help` choices and `supported_effort_values`, and no model-embedded intensity is already confirmed. Omit this question and never emit `PRIZMKIT_EFFORT` under Branches 1–3, empty intersection, or model-embedded intensity. If the user supplies a `MODEL` containing embedded intensity in this same Step 3 round under Branch 4, omit `PRIZMKIT_EFFORT` by default and explain that intensity is already encoded in `MODEL` so conflicting settings are not sent together.
|
|
93
|
+
- **Customize other default parameters?** — `No (Recommended — use all defaults from the table)` or `Yes — customize specific defaults`.
|
|
94
|
+
4. **Conditional customization follow-up (only when Yes)**: if the user selects `Yes — customize specific defaults`, issue one follow-up `AskUserQuestion` call to collect only the specific table parameters to override, validate values (boolean `VERBOSE` / `STOP_ON_FAILURE`, non-negative integer `MAX_RETRIES`), and apply them to the command. Do not ask routine defaults one by one when the user chooses `No`.
|
|
87
95
|
|
|
88
96
|
### Step 4: Build command fragments
|
|
89
97
|
|
|
90
|
-
|
|
98
|
+
Map confirmed choices to environment variables per `${SKILL_DIR}/references/configuration.md`:
|
|
99
|
+
- When defaults from the table are kept, emit `VERBOSE=1 MAX_RETRIES=3` (foreground) or `--env "VERBOSE=1 MAX_RETRIES=3"` (daemon), and omit runtime-default `STOP_ON_FAILURE=1`.
|
|
100
|
+
- When the user disables stop-on-failure, explicitly emit `STOP_ON_FAILURE=0`. When the user disables verbose logging, emit `VERBOSE=0` or omit `VERBOSE`.
|
|
101
|
+
- Preserve parameterized `MODEL` foreground/daemon quoting rules and any temporary `AI_CLI=<cli>` override.
|
|
91
102
|
|
|
92
103
|
Return this prerequisite-check command separately from the pipeline command:
|
|
93
104
|
|
|
@@ -95,18 +106,18 @@ Return this prerequisite-check command separately from the pipeline command:
|
|
|
95
106
|
python3 ./.prizmkit/dev-pipeline/cli.py diagnostics version && git --version
|
|
96
107
|
```
|
|
97
108
|
|
|
98
|
-
Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even
|
|
109
|
+
Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even though start-time read-only probing ran during configuration, pipeline commands are never executed by this skill.
|
|
99
110
|
|
|
100
111
|
### Step 5: Return the start command
|
|
101
112
|
|
|
102
|
-
Foreground template:
|
|
113
|
+
Foreground template (table defaults kept):
|
|
103
114
|
|
|
104
115
|
```bash
|
|
105
116
|
VERBOSE=1 MAX_RETRIES=3 \
|
|
106
117
|
python3 ./.prizmkit/dev-pipeline/cli.py run bugfix .prizmkit/plans/bug-fix-list.json
|
|
107
118
|
```
|
|
108
119
|
|
|
109
|
-
Background template:
|
|
120
|
+
Background template (table defaults kept):
|
|
110
121
|
|
|
111
122
|
```bash
|
|
112
123
|
python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json \
|
|
@@ -204,7 +215,7 @@ For every request, return:
|
|
|
204
215
|
2. Input plan path and selected IDs, when applicable.
|
|
205
216
|
3. Assumptions and safety warnings.
|
|
206
217
|
4. Exact command block.
|
|
207
|
-
5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (
|
|
218
|
+
5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (non-start intent)>`
|
|
208
219
|
6. `Pipeline execution: not performed by this skill; run any command above manually when ready.`
|
|
209
220
|
|
|
210
221
|
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,6 +1,6 @@
|
|
|
1
1
|
# Configuration Reference — Bugfix Pipeline Command Builder
|
|
2
2
|
|
|
3
|
-
Use this reference to run bounded
|
|
3
|
+
Use this reference to run start-time bounded read-only AI CLI capability probing, present the Default Parameters Overview Table, apply the four ordered adaptive placement branches, 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
|
|
|
@@ -14,38 +14,44 @@ python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
|
|
|
14
14
|
|
|
15
15
|
`diagnostics ai-cli` reports `detected_cli`, `platform`, `source`, `runtime_mode`, `model_arg_supported`, `effort_flag_mode`, `supported_effort_values`, and `cli_available`, and exits non-zero if no AI CLI can be resolved (`detected_cli: (not found)`).
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## Start-Time Read-Only CLI Capability Probe
|
|
18
18
|
|
|
19
|
-
- **
|
|
20
|
-
- **
|
|
21
|
-
1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` — or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` whenever the user explicitly specifies a
|
|
19
|
+
- **Non-start intents (skip probing)**: For `status`, `logs`, `stop`, and `retry` intents, skip all read-only CLI probing (`diagnostics ai-cli` and `--help`) and output `Read-only CLI probe: skipped (non-start intent)`.
|
|
20
|
+
- **Start intent probe sequence**: Immediately after Step 2 execution-mode confirmation on every Start intent (before presenting Step 3 model/effort choices), execute this bounded read-only sequence:
|
|
21
|
+
1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` — or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` whenever the user explicitly specifies a temporary `AI_CLI=<cli>` override (and preserve `AI_CLI=<cli>` in the returned launch command) — then read the structured capability fields directly: `detected_cli`, `platform`, `source`, `model_arg_supported` (`true`|`false`), `effort_flag_mode` (`flag`|`config`|`none`|`custom_ignored`), `supported_effort_values` (comma-separated values or `none`), and `cli_available` (`true`|`false`). 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
22
|
2. If `effort_flag_mode` is `custom_ignored`, route directly to Branch 2 without requiring `<cli> --help`.
|
|
23
23
|
3. Otherwise, verify that `cli_available` is `true` and 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
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:`.
|
|
25
25
|
|
|
26
|
-
##
|
|
26
|
+
## Default Parameters Overview Table
|
|
27
27
|
|
|
28
|
-
|
|
29
|
-
|---|---|
|
|
30
|
-
| Verbose Off | `VERBOSE=0` |
|
|
31
|
-
| Verbose On | `VERBOSE=1` |
|
|
32
|
-
| Max retries N | `MAX_RETRIES=N` |
|
|
28
|
+
Display this table at the start of Step 3 (noting any pre-specified temporary `AI_CLI=<cli>` override as already specified so it is carried forward without re-asking):
|
|
33
29
|
|
|
34
|
-
|
|
30
|
+
| Parameter | Default | Meaning |
|
|
31
|
+
|---|---|---|
|
|
32
|
+
| `VERBOSE` | `1` | Enable verbose runtime session logging (runtime default is `0`; launcher emits `VERBOSE=1` by default) |
|
|
33
|
+
| `MAX_RETRIES` | `3` | Maximum retry attempts per task before marking failed |
|
|
34
|
+
| `STOP_ON_FAILURE` | `1` | Stop subsequent pipeline execution immediately when a task fails (runtime default; omit when kept, emit `STOP_ON_FAILURE=0` to continue to other eligible tasks) |
|
|
35
35
|
|
|
36
|
-
|
|
36
|
+
## Focused Configuration Flow
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
2. **Model (`MODEL`)**
|
|
38
|
+
Collect configuration in one focused round after showing the Default Parameters Overview Table. Always configure `MODEL` before `PRIZMKIT_EFFORT`:
|
|
39
|
+
|
|
40
|
+
1. **Model (`MODEL`)**
|
|
42
41
|
- Default — omit `MODEL` so the resolved AI CLI uses its default model.
|
|
43
42
|
- 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
43
|
- 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
44
|
- **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
|
-
|
|
47
|
-
-
|
|
48
|
-
-
|
|
45
|
+
2. **Reasoning effort (`PRIZMKIT_EFFORT`)** *(conditional — Branch 4 only)*
|
|
46
|
+
- Ask and emit `PRIZMKIT_EFFORT` strictly from the four ordered placement branches below (never hardcode one universal effort list or CLI allowlist).
|
|
47
|
+
- Omit the question and never emit `PRIZMKIT_EFFORT` under Branches 1–3, empty capability intersection, or model-embedded intensity syntax.
|
|
48
|
+
- Default under Branch 4 — omit `PRIZMKIT_EFFORT`.
|
|
49
|
+
3. **Customize other default parameters?**
|
|
50
|
+
- `No (Recommended — use all defaults from the table)` — apply table defaults directly without asking routine parameters one by one.
|
|
51
|
+
- `Yes — customize specific defaults` — ask one follow-up prompt collecting and validating only the specific table overrides:
|
|
52
|
+
- `VERBOSE`: boolean (`1` to enable; `0` or omit `VERBOSE` to disable).
|
|
53
|
+
- `MAX_RETRIES`: non-negative integer `N` (`MAX_RETRIES=N`).
|
|
54
|
+
- `STOP_ON_FAILURE`: boolean (`1` runtime default — omit; `0` explicitly emit `STOP_ON_FAILURE=0` to continue to other eligible tasks after a failure).
|
|
49
55
|
|
|
50
56
|
## Adaptive Placement Branches (Evaluate 1 → 4 Strictly in Order)
|
|
51
57
|
|
|
@@ -53,21 +59,21 @@ Evaluate branches strictly from 1 to 4 using `diagnostics ai-cli` capability fie
|
|
|
53
59
|
|
|
54
60
|
1. **Branch 1 — Probe failed, CLI missing, or insufficient help output**:
|
|
55
61
|
- Condition: `diagnostics ai-cli` fails or exits non-zero, `detected_cli` is `(not found)` or missing on `PATH`, `cli_available` is `false`, required capability fields (`model_arg_supported`, `effort_flag_mode`, `supported_effort_values`, `cli_available`) 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
|
|
62
|
+
- Action: Never guess or synthesize `PRIZMKIT_EFFORT`. Omit the `PRIZMKIT_EFFORT` question and variable, 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
63
|
2. **Branch 2 — Model-embedded intensity syntax or `custom_ignored` profile**:
|
|
58
64
|
- 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
|
|
65
|
+
- Action: Omit the `PRIZMKIT_EFFORT` question and variable. 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 leave `MODEL` unset 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
66
|
3. **Branch 3 — Independent effort explicitly unsupported**:
|
|
61
67
|
- 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`.
|
|
68
|
+
- Action: Do not ask for or 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
69
|
4. **Branch 4 — Independent effort compatible**:
|
|
64
70
|
- 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). If the confirmed `MODEL` value
|
|
71
|
+
- Action: When live `--help` enumerates concrete effort/thinking values, intersect those enumerated choices with `supported_effort_values`; if the intersection is empty, omit the `PRIZMKIT_EFFORT` question and variable 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). If the confirmed `MODEL` value (including one supplied in the same Step 3 round) already embeds a reasoning-effort suffix or parameter, omit `PRIZMKIT_EFFORT` by default and include a conflict-avoidance notice explaining that intensity is already encoded in `MODEL` so conflicting settings are not sent together.
|
|
66
72
|
|
|
67
73
|
## Command Construction Rules
|
|
68
74
|
|
|
69
|
-
- Foreground: place environment assignments (`AI_CLI=...` when overridden, `VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE
|
|
70
|
-
- Background daemon: place environment assignments inside one `--env "..."` value.
|
|
75
|
+
- Foreground: place environment assignments (`AI_CLI=...` when overridden, `VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE=0` when disabled, `MODEL=...`, `PRIZMKIT_EFFORT=...`) before `python3`. Default table values emit `VERBOSE=1 MAX_RETRIES=3` and omit `STOP_ON_FAILURE=1` because Runtime defaults `STOP_ON_FAILURE` to `1`.
|
|
76
|
+
- Background daemon: place environment assignments inside one `--env "..."` value. Default table values emit `--env "VERBOSE=1 MAX_RETRIES=3"` and omit `STOP_ON_FAILURE=1`.
|
|
71
77
|
- **Parameterized `MODEL` quoting**:
|
|
72
78
|
- Foreground: single-quote parameterized `MODEL` values containing colons, square brackets, parentheses, spaces, commas, or shell metacharacters:
|
|
73
79
|
```bash
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: "feature-pipeline-launcher"
|
|
3
|
-
description: "Build feature-pipeline commands from a validated .prizmkit/plans/feature-list.json without executing the pipeline.
|
|
3
|
+
description: "Build feature-pipeline commands from a validated .prizmkit/plans/feature-list.json without executing the pipeline. Runs start-time bounded read-only AI CLI model/effort capability probing (skipped on non-start intents) 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.
|
|
8
|
+
Build commands for the autonomous feature pipeline from within an AI CLI conversation. On start intents, this skill reads planning inputs, runs bounded start-time read-only AI CLI capability probing after execution-mode selection, displays a Default Parameters Overview Table, asks one focused configuration round (`MODEL`, conditional `PRIZMKIT_EFFORT`, and whether to customize other defaults), displays the command and its effects, then stops. Non-start intents skip CLI probing.
|
|
9
9
|
|
|
10
10
|
## Execution Boundary
|
|
11
11
|
|
|
@@ -15,7 +15,7 @@ This skill separates bounded read-only configuration probing from pipeline execu
|
|
|
15
15
|
- read a validated feature list and relevant configuration;
|
|
16
16
|
- build prerequisite-check, start, status, logs, stop, and retry commands;
|
|
17
17
|
- explain command effects and destructive options before returning them;
|
|
18
|
-
-
|
|
18
|
+
- on every Start intent (after Step 2 execution-mode selection): run bounded, side-effect-free read-only probes — `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` (or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` when a temporary `AI_CLI=<cli>` override is given), route `effort_flag_mode: custom_ignored` directly to Branch 2, otherwise verify `cli_available: true` and executable availability 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. Non-start intents (`status`, `logs`, `stop`, `retry`) skip read-only probing and record `Read-only CLI probe: skipped (non-start intent)`.
|
|
19
19
|
- **Prohibited (pipeline execution and state mutation)**:
|
|
20
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.
|
|
21
21
|
|
|
@@ -28,7 +28,7 @@ Use this skill for:
|
|
|
28
28
|
- constructing a foreground or background-daemon feature pipeline command;
|
|
29
29
|
- selecting a feature subset such as `F-001:F-005` or `F-001,F-003`;
|
|
30
30
|
- constructing status, logs, stop, or retry commands;
|
|
31
|
-
- translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`,
|
|
31
|
+
- translating user-selected runtime options (`MODEL`, adaptive `PRIZMKIT_EFFORT`, and optional default overrides) into environment variables.
|
|
32
32
|
|
|
33
33
|
Do not use it to:
|
|
34
34
|
|
|
@@ -51,13 +51,13 @@ Classify the request before asking configuration questions:
|
|
|
51
51
|
|
|
52
52
|
| Intent | Output |
|
|
53
53
|
|---|---|
|
|
54
|
-
| Start all or selected features | Prerequisite-check command plus one start command |
|
|
55
|
-
| Check status | Daemon status and item-level status commands |
|
|
56
|
-
| Show logs | Recent or follow-log command |
|
|
57
|
-
| Stop | Daemon stop command plus optional status command |
|
|
58
|
-
| Retry failed feature work | State-only, preserve-runtime, fresh-checkout, or clean reset plus a separate run command with safety disclosure |
|
|
54
|
+
| Start all or selected features | Prerequisite-check command plus one start command (runs start-time read-only CLI probe) |
|
|
55
|
+
| Check status | Daemon status and item-level status commands (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
56
|
+
| Show logs | Recent or follow-log command (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
57
|
+
| Stop | Daemon stop command plus optional status command (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
58
|
+
| Retry failed feature work | State-only, preserve-runtime, fresh-checkout, or clean reset plus a separate run command with safety disclosure (`Read-only CLI probe: skipped (non-start intent)`) |
|
|
59
59
|
|
|
60
|
-
Only the start intent uses the execution-mode and configuration rounds.
|
|
60
|
+
Only the start intent uses the execution-mode, start-time CLI probe, and configuration rounds. Non-start intents (`status`, `logs`, `stop`, `retry`) skip probing and emit `Read-only CLI probe: skipped (non-start intent)`.
|
|
61
61
|
|
|
62
62
|
## Start Command Workflow
|
|
63
63
|
|
|
@@ -65,7 +65,7 @@ Only the start intent uses the execution-mode and configuration rounds.
|
|
|
65
65
|
|
|
66
66
|
1. Resolve the feature-list path.
|
|
67
67
|
2. Read the list and summarize total, eligible, blocked, and selected feature IDs.
|
|
68
|
-
3. Preserve
|
|
68
|
+
3. Preserve any pre-specified `--features` subset or temporary `AI_CLI=<cli>` override directly; carry them forward into the Default Parameters Overview Table and final command without re-asking. Do not invent a subset.
|
|
69
69
|
4. If an existing run is suspected from user context, include a status command in the output; do not run it.
|
|
70
70
|
|
|
71
71
|
### Step 2: Ask execution mode
|
|
@@ -75,23 +75,31 @@ Use one `AskUserQuestion` call with exactly one question:
|
|
|
75
75
|
- **Foreground (Recommended)** — build `run feature`; output remains attached to the user's terminal.
|
|
76
76
|
- **Background daemon** — build `daemon feature start`; the runtime manages detached execution and logs.
|
|
77
77
|
|
|
78
|
-
Wait for the response before
|
|
78
|
+
Wait for the response before Step 3.
|
|
79
79
|
|
|
80
|
-
### Step 3:
|
|
80
|
+
### Step 3: Probe CLI capabilities, show default parameters, and ask focused configuration
|
|
81
81
|
|
|
82
|
-
|
|
82
|
+
1. Load `${SKILL_DIR}/references/configuration.md` and run its start-time bounded read-only AI CLI capability probe sequence first: execute `diagnostics ai-cli` (honoring any temporary `AI_CLI=<cli>` override), consume structured capability fields directly with zero legacy fallback parsing, route `effort_flag_mode: custom_ignored` directly to Branch 2 without letting `<cli> --help` trigger Branch 1, otherwise verify `cli_available: true` and executable availability on `PATH`, and inspect `<cli> --help` (plus `<cli> exec --help` when applicable).
|
|
83
|
+
2. Display the **Default Parameters Overview Table** before asking configuration questions (noting any pre-specified `--features` or `AI_CLI` values as already specified):
|
|
83
84
|
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
85
|
+
| Parameter | Default | Meaning |
|
|
86
|
+
|---|---|---|
|
|
87
|
+
| `VERBOSE` | `1` | Enable verbose runtime session logging |
|
|
88
|
+
| `MAX_RETRIES` | `3` | Maximum retry attempts per task before marking failed |
|
|
89
|
+
| `STOP_ON_FAILURE` | `1` | Stop subsequent pipeline execution immediately when a task fails (runtime default; override with `STOP_ON_FAILURE=0` to continue to other eligible tasks) |
|
|
87
90
|
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
+
3. Then use a separate `AskUserQuestion` call covering only:
|
|
92
|
+
- **`MODEL`** — Default (omit `MODEL` to use the CLI default) or explicit/parameterized model name guided by probe evidence. Under `effort_flag_mode: custom_ignored` or `model_arg_supported: false`, warn clearly per the reference and leave `MODEL` unset. Remember that an individual feature's `"model"` field in `.prizmkit/plans/feature-list.json` takes precedence over global `MODEL`.
|
|
93
|
+
- **`PRIZMKIT_EFFORT`** *(conditional — Branch 4 only)* — ask **only** when Branch 4 of the four ordered adaptive placement branches matches with a non-empty intersection of live `--help` choices and `supported_effort_values`, and no model-embedded intensity is already confirmed. Omit this question and never emit `PRIZMKIT_EFFORT` under Branches 1–3, empty intersection, or model-embedded intensity. If the user supplies a `MODEL` containing embedded intensity in this same Step 3 round under Branch 4, omit `PRIZMKIT_EFFORT` by default and explain that intensity is already encoded in `MODEL` so conflicting settings are not sent together.
|
|
94
|
+
- **Customize other default parameters?** — `No (Recommended — use all defaults from the table)` or `Yes — customize specific defaults`.
|
|
95
|
+
4. **Conditional customization follow-up (only when Yes)**: if the user selects `Yes — customize specific defaults`, issue one follow-up `AskUserQuestion` call to collect only the specific table parameters to override, validate values (boolean `VERBOSE` / `STOP_ON_FAILURE`, non-negative integer `MAX_RETRIES`), and apply them to the command. Do not ask routine defaults one by one when the user chooses `No`.
|
|
91
96
|
|
|
92
97
|
### Step 4: Build command fragments
|
|
93
98
|
|
|
94
|
-
|
|
99
|
+
Map confirmed choices to environment variables per `${SKILL_DIR}/references/configuration.md`:
|
|
100
|
+
- When defaults from the table are kept, emit `VERBOSE=1 MAX_RETRIES=3` (foreground) or `--env "VERBOSE=1 MAX_RETRIES=3"` (daemon), and omit runtime-default `STOP_ON_FAILURE=1`.
|
|
101
|
+
- When the user disables stop-on-failure, explicitly emit `STOP_ON_FAILURE=0`. When the user disables verbose logging, emit `VERBOSE=0` or omit `VERBOSE`.
|
|
102
|
+
- Preserve parameterized `MODEL` foreground/daemon quoting rules and any temporary `AI_CLI=<cli>` override.
|
|
95
103
|
|
|
96
104
|
Build the prerequisite-check command separately from the pipeline command so the user can inspect each action:
|
|
97
105
|
|
|
@@ -99,11 +107,11 @@ Build the prerequisite-check command separately from the pipeline command so the
|
|
|
99
107
|
python3 ./.prizmkit/dev-pipeline/cli.py diagnostics version && git --version
|
|
100
108
|
```
|
|
101
109
|
|
|
102
|
-
Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even
|
|
110
|
+
Also include the configured AI CLI check fragment from the reference so the user can verify prerequisites in their own shell. Even though start-time read-only probing ran during configuration, pipeline commands are never executed by this skill.
|
|
103
111
|
|
|
104
112
|
### Step 5: Return the start command
|
|
105
113
|
|
|
106
|
-
Foreground template:
|
|
114
|
+
Foreground template (table defaults kept):
|
|
107
115
|
|
|
108
116
|
```bash
|
|
109
117
|
VERBOSE=1 MAX_RETRIES=3 \
|
|
@@ -117,7 +125,7 @@ VERBOSE=1 MAX_RETRIES=3 \
|
|
|
117
125
|
python3 ./.prizmkit/dev-pipeline/cli.py run feature .prizmkit/plans/feature-list.json --features F-001:F-005
|
|
118
126
|
```
|
|
119
127
|
|
|
120
|
-
Background template:
|
|
128
|
+
Background template (table defaults kept):
|
|
121
129
|
|
|
122
130
|
```bash
|
|
123
131
|
python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json \
|
|
@@ -222,7 +230,7 @@ For every request, return:
|
|
|
222
230
|
2. Input plan path and selected IDs, when applicable.
|
|
223
231
|
3. Assumptions and safety warnings.
|
|
224
232
|
4. Exact command block.
|
|
225
|
-
5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (
|
|
233
|
+
5. `Read-only CLI probe: <diagnostics-and-help-summary | skipped (non-start intent)>`
|
|
226
234
|
6. `Pipeline execution: not performed by this skill; run any command above manually when ready.`
|
|
227
235
|
|
|
228
236
|
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,6 +1,6 @@
|
|
|
1
1
|
# Configuration Reference — Feature Pipeline Command Builder
|
|
2
2
|
|
|
3
|
-
Use this reference to run bounded
|
|
3
|
+
Use this reference to run start-time bounded read-only AI CLI capability probing, present the Default Parameters Overview Table, apply the four ordered adaptive placement branches, 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
|
|
|
@@ -14,38 +14,44 @@ python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli
|
|
|
14
14
|
|
|
15
15
|
`diagnostics ai-cli` reports `detected_cli`, `platform`, `source`, `runtime_mode`, `model_arg_supported`, `effort_flag_mode`, `supported_effort_values`, and `cli_available`, and exits non-zero if no AI CLI can be resolved (`detected_cli: (not found)`).
|
|
16
16
|
|
|
17
|
-
##
|
|
17
|
+
## Start-Time Read-Only CLI Capability Probe
|
|
18
18
|
|
|
19
|
-
- **
|
|
20
|
-
- **
|
|
21
|
-
1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` — or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` whenever the user explicitly specifies a
|
|
19
|
+
- **Non-start intents (skip probing)**: For `status`, `logs`, `stop`, and `retry` intents, skip all read-only CLI probing (`diagnostics ai-cli` and `--help`) and output `Read-only CLI probe: skipped (non-start intent)`.
|
|
20
|
+
- **Start intent probe sequence**: Immediately after Step 2 execution-mode confirmation on every Start intent (before presenting Step 3 model/effort choices), execute this bounded read-only sequence:
|
|
21
|
+
1. Run `python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` — or `AI_CLI=<cli> python3 ./.prizmkit/dev-pipeline/cli.py diagnostics ai-cli` whenever the user explicitly specifies a temporary `AI_CLI=<cli>` override (and preserve `AI_CLI=<cli>` in the returned launch command) — then read the structured capability fields directly: `detected_cli`, `platform`, `source`, `model_arg_supported` (`true`|`false`), `effort_flag_mode` (`flag`|`config`|`none`|`custom_ignored`), `supported_effort_values` (comma-separated values or `none`), and `cli_available` (`true`|`false`). 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
22
|
2. If `effort_flag_mode` is `custom_ignored`, route directly to Branch 2 without requiring `<cli> --help`.
|
|
23
23
|
3. Otherwise, verify that `cli_available` is `true` and 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
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:`.
|
|
25
25
|
|
|
26
|
-
##
|
|
26
|
+
## Default Parameters Overview Table
|
|
27
27
|
|
|
28
|
-
|
|
29
|
-
|---|---|
|
|
30
|
-
| Verbose Off | `VERBOSE=0` |
|
|
31
|
-
| Verbose On | `VERBOSE=1` |
|
|
32
|
-
| Max retries N | `MAX_RETRIES=N` |
|
|
28
|
+
Display this table at the start of Step 3 (noting any pre-specified `--features` filter or temporary `AI_CLI=<cli>` override as already specified so it is carried forward without re-asking):
|
|
33
29
|
|
|
34
|
-
|
|
30
|
+
| Parameter | Default | Meaning |
|
|
31
|
+
|---|---|---|
|
|
32
|
+
| `VERBOSE` | `1` | Enable verbose runtime session logging (runtime default is `0`; launcher emits `VERBOSE=1` by default) |
|
|
33
|
+
| `MAX_RETRIES` | `3` | Maximum retry attempts per task before marking failed |
|
|
34
|
+
| `STOP_ON_FAILURE` | `1` | Stop subsequent pipeline execution immediately when a task fails (runtime default; omit when kept, emit `STOP_ON_FAILURE=0` to continue to other eligible tasks) |
|
|
35
35
|
|
|
36
|
-
|
|
36
|
+
## Focused Configuration Flow
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
2. **Model (`MODEL`)**
|
|
38
|
+
Collect configuration in one focused round after showing the Default Parameters Overview Table. Always configure `MODEL` before `PRIZMKIT_EFFORT`:
|
|
39
|
+
|
|
40
|
+
1. **Model (`MODEL`)**
|
|
42
41
|
- Default — omit `MODEL` so the resolved AI CLI uses its default model.
|
|
43
42
|
- 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
43
|
- 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
44
|
- **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
|
-
|
|
47
|
-
-
|
|
48
|
-
-
|
|
45
|
+
2. **Reasoning effort (`PRIZMKIT_EFFORT`)** *(conditional — Branch 4 only)*
|
|
46
|
+
- Ask and emit `PRIZMKIT_EFFORT` strictly from the four ordered placement branches below (never hardcode one universal effort list or CLI allowlist).
|
|
47
|
+
- Omit the question and never emit `PRIZMKIT_EFFORT` under Branches 1–3, empty capability intersection, or model-embedded intensity syntax.
|
|
48
|
+
- Default under Branch 4 — omit `PRIZMKIT_EFFORT`.
|
|
49
|
+
3. **Customize other default parameters?**
|
|
50
|
+
- `No (Recommended — use all defaults from the table)` — apply table defaults directly without asking routine parameters one by one.
|
|
51
|
+
- `Yes — customize specific defaults` — ask one follow-up prompt collecting and validating only the specific table overrides:
|
|
52
|
+
- `VERBOSE`: boolean (`1` to enable; `0` or omit `VERBOSE` to disable).
|
|
53
|
+
- `MAX_RETRIES`: non-negative integer `N` (`MAX_RETRIES=N`).
|
|
54
|
+
- `STOP_ON_FAILURE`: boolean (`1` runtime default — omit; `0` explicitly emit `STOP_ON_FAILURE=0` to continue to other eligible tasks after a failure).
|
|
49
55
|
|
|
50
56
|
## Adaptive Placement Branches (Evaluate 1 → 4 Strictly in Order)
|
|
51
57
|
|
|
@@ -53,21 +59,21 @@ Evaluate branches strictly from 1 to 4 using `diagnostics ai-cli` capability fie
|
|
|
53
59
|
|
|
54
60
|
1. **Branch 1 — Probe failed, CLI missing, or insufficient help output**:
|
|
55
61
|
- Condition: `diagnostics ai-cli` fails or exits non-zero, `detected_cli` is `(not found)` or missing on `PATH`, `cli_available` is `false`, required capability fields (`model_arg_supported`, `effort_flag_mode`, `supported_effort_values`, `cli_available`) 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
|
|
62
|
+
- Action: Never guess or synthesize `PRIZMKIT_EFFORT`. Omit the `PRIZMKIT_EFFORT` question and variable, 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
63
|
2. **Branch 2 — Model-embedded intensity syntax or `custom_ignored` profile**:
|
|
58
64
|
- 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
|
|
65
|
+
- Action: Omit the `PRIZMKIT_EFFORT` question and variable. 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 leave `MODEL` unset 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
66
|
3. **Branch 3 — Independent effort explicitly unsupported**:
|
|
61
67
|
- 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`.
|
|
68
|
+
- Action: Do not ask for or 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
69
|
4. **Branch 4 — Independent effort compatible**:
|
|
64
70
|
- 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). If the confirmed `MODEL` value
|
|
71
|
+
- Action: When live `--help` enumerates concrete effort/thinking values, intersect those enumerated choices with `supported_effort_values`; if the intersection is empty, omit the `PRIZMKIT_EFFORT` question and variable 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). If the confirmed `MODEL` value (including one supplied in the same Step 3 round) already embeds a reasoning-effort suffix or parameter, omit `PRIZMKIT_EFFORT` by default and include a conflict-avoidance notice explaining that intensity is already encoded in `MODEL` so conflicting settings are not sent together.
|
|
66
72
|
|
|
67
73
|
## Command Construction Rules
|
|
68
74
|
|
|
69
|
-
- Foreground: place environment assignments (`AI_CLI=...` when overridden, `VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE
|
|
70
|
-
- Background daemon: place environment assignments inside one `--env "..."` value.
|
|
75
|
+
- Foreground: place environment assignments (`AI_CLI=...` when overridden, `VERBOSE=...`, `MAX_RETRIES=...`, `STOP_ON_FAILURE=0` when disabled, `MODEL=...`, `PRIZMKIT_EFFORT=...`) before `python3`. Default table values emit `VERBOSE=1 MAX_RETRIES=3` and omit `STOP_ON_FAILURE=1` because Runtime defaults `STOP_ON_FAILURE` to `1`.
|
|
76
|
+
- Background daemon: place environment assignments inside one `--env "..."` value. Default table values emit `--env "VERBOSE=1 MAX_RETRIES=3"` and omit `STOP_ON_FAILURE=1`.
|
|
71
77
|
- **Parameterized `MODEL` quoting**:
|
|
72
78
|
- Foreground: single-quote parameterized `MODEL` values containing colons, square brackets, parentheses, spaces, commas, or shell metacharacters:
|
|
73
79
|
```bash
|
|
@@ -39,7 +39,7 @@ Every new/changed feature must execute cleanly in a fresh AI session without con
|
|
|
39
39
|
|
|
40
40
|
## Prerequisites & Reference Loading
|
|
41
41
|
|
|
42
|
-
1. Load `${SKILL_DIR}/assets/planning-guide.md` before writing descriptions; load `${SKILL_DIR}/references/incremental-feature-planning.md` for incremental mode, `${SKILL_DIR}/references/completeness-review.md` for Phase 6, and `${SKILL_DIR}/references/new-project-planning.md` / `decomposition-patterns.md` / `
|
|
42
|
+
1. Load `${SKILL_DIR}/assets/planning-guide.md` before writing descriptions; load `${SKILL_DIR}/references/incremental-feature-planning.md` for incremental mode, `${SKILL_DIR}/references/completeness-review.md` for Phase 6, and `${SKILL_DIR}/references/new-project-planning.md` / `decomposition-patterns.md` / `error-recovery.md` when triggered.
|
|
43
43
|
2. Check optional workspace files (never block if absent): `.prizmkit/prizm-docs/root.prizm`, `.prizmkit/config.json` (pre-fill `global_context` from `tech_stack`: `language`, `frontend_framework`, `frontend_styling`, `backend_framework`, `database`, `orm`, `testing` → `testing_strategy`, `bundler`, `runtime`; confirm detected stack instead of re-asking), `.prizmkit/plans/project-brief.md`, existing `.prizmkit/plans/feature-list.json` (bounded commands only), and the current host's conventional project-local instruction file when present (non-exhaustive examples: `AGENTS.md`, `CLAUDE.md`, `CODEBUDDY.md`, `.pi/APPEND_SYSTEM.md`) for project conventions and architecture decisions. If `root.prizm` is absent, scan shallow project directories excluding `.git`, `.prizmkit`, platform dirs, and build/vendor folders.
|
|
44
44
|
3. Always validate via script (`validate-and-generate.py`); use its manual checklist fallback in `references/completeness-review.md` only if unavailable.
|
|
45
45
|
|
|
@@ -68,13 +68,13 @@ For ordinary incremental planning, NEVER read the complete existing `.prizmkit/p
|
|
|
68
68
|
1.2 **Upfront Material Detection (Hard Rule)**: if user supplied materials (paths, URLs, specs, code), acknowledge ("I received the following materials: [list]"), read/fetch all immediately, AND still ask "Are there any additional materials you'd like to provide?". If none supplied yet, ask once covering code paths, design docs/PRDs, `.prizmkit/prizm-docs/`/READMEs, images, and web links. Normalize task-relevant evidence cleanly: Material ingestion follows the same durability rule as final output (retain purpose-tagged stable refs/excerpts, omit transient non-code paths).
|
|
69
69
|
2. **Confirm constraints & architecture** from `root.prizm`/project context and populate `global_context`.
|
|
70
70
|
3. **Contract-bounded feature table (CP-FP-2)**: merge items sharing one contract-bounded capability before showing the first user-facing table (complaints/walkthrough notes/UI states are not one ID per row; split only at heavy capability seams exceeding one headless session).
|
|
71
|
-
4. **Refine contracts
|
|
71
|
+
4. **Refine contracts**: run per-feature clarification for consequential behavioral/scope/integration/evidence ambiguity (never force confirmation on safe unconstrained internals).
|
|
72
72
|
5. **DAG & Priority/Complexity Calibration (CP-FP-3)**: prevent uniform `high/high` collapse (follow the rubric and `ID | Title | Priority | Priority Rationale | Complexity | Complexity Rationale` table in `${SKILL_DIR}/references/completeness-review.md`).
|
|
73
73
|
6. **Headless Context Completeness Gate (CP-FP-3.3, Phase 6)**: read `${SKILL_DIR}/references/completeness-review.md` and run the mandatory Pre-Generation Completeness Review on every new/changed feature (`description` + `acceptance_criteria` must answer all 12 questions alone; return `NEEDS_FIXES` and fix before proceeding; do not bulk-rewrite untouched history).
|
|
74
74
|
7. **Draft batch & testing defaults (CP-FP-3.2, CP-FP-4)**: write `.prizmkit/plans/feature-list.draft.json` using `context` IDs and apply Phase 8 testing expectations.
|
|
75
75
|
8. **Validate & Local Generated-Plan Review Gate (CP-FP-5 → CP-FP-6)**: run draft validation + `--dry-run`, run §Local Generated-Plan Review Gate until `PASS`, then insert once (`append` or `generate`), complete §Draft Lifecycle cleanup, and present handoff.
|
|
76
76
|
|
|
77
|
-
**Checkpoints**: **CP-FP-1** Scope Confirmed (1) · **CP-FP-2** Contract-Grained Proposals (3-5) · **CP-FP-3** DAG Validity (5) · **CP-FP-3.
|
|
77
|
+
**Checkpoints**: **CP-FP-1** Scope Confirmed (1) · **CP-FP-2** Contract-Grained Proposals (3-5) · **CP-FP-3** DAG Validity (5) · **CP-FP-3.2** Testing Defaults (7) · **CP-FP-3.3** Completeness Review Passed (6) · **CP-FP-4** Draft Batch Ready (7-8) · **CP-FP-5** Draft Validation + Dry-Run Pass (9) · **CP-FP-6** Reviewed, Then Inserted Once (`generated-plan-review.md` reviewed draft batch → accepted fixes → revalidated → `PASS` → single `append`/`generate` matching `appended_ids` → draft removed; 10-11). If resuming prior artifacts, read `${SKILL_DIR}/references/error-recovery.md`.
|
|
78
78
|
|
|
79
79
|
## Fast Path (Simple Incremental)
|
|
80
80
|
|
|
@@ -85,12 +85,6 @@ Eligible only when ALL apply: incremental mode, `1-2` features max, each `<=5` c
|
|
|
85
85
|
4. Write additions-only draft and check merge feasibility (`--dry-run`). If invalid, fix the additions-only draft and re-run the dry run (max 2 attempts, then escalate to full workflow).
|
|
86
86
|
5. Run §Local Generated-Plan Review Gate on the draft (`PASS`), insert once with `append`, complete §Draft Lifecycle cleanup, and present handoff.
|
|
87
87
|
|
|
88
|
-
## Browser Interaction Planning
|
|
89
|
-
|
|
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
|
-
|
|
94
88
|
## Output Rules & Local Generated-Plan Review Gate
|
|
95
89
|
|
|
96
90
|
Write via `generate` (complete new draft) or `append` (additions-only batch) — **never hand-write `.prizmkit/plans/feature-list.json`**:
|
|
@@ -109,7 +103,7 @@ Read `${SKILL_DIR}/references/generated-plan-review.md` and follow it as the sin
|
|
|
109
103
|
|
|
110
104
|
## Testing, Error Recovery, Session Exit & Handoff
|
|
111
105
|
|
|
112
|
-
- **Testing Defaults (Phase 8)**: Assign testing expectations matching risk (`high`: scoped tests + review-gate evidence; `medium`: focused changed-behavior tests; `low`: smallest relevant verification)
|
|
106
|
+
- **Testing Defaults (Phase 8)**: Assign testing expectations matching risk (`high`: scoped tests + review-gate evidence; `medium`: focused changed-behavior tests; `low`: smallest relevant verification); present consolidated summary for confirmation.
|
|
113
107
|
- **Next-Step Execution Policy**: Recommend `feature-pipeline-launcher`; never recommend manual runtime shell scripts or auto-execute.
|
|
114
108
|
- **Error Recovery & Resume**: On validation failures (max 3 retries on critical errors; clarify consequential warnings; proceed past informational warnings) or interruptions, read `${SKILL_DIR}/references/error-recovery.md`.
|
|
115
109
|
- **Session Exit Gate**: If user intended `.prizmkit/plans/feature-list.json` and phase `< 7` with no valid list written, remind and ask `AskUserQuestion` (`Continue to completion (Recommended)`, `Save draft & exit` retaining `.prizmkit/plans/feature-list.draft.json`, `Abandon`).
|