prizmkit 1.0.7 → 1.0.8

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.
@@ -1,5 +1,5 @@
1
1
  {
2
- "frameworkVersion": "1.0.7",
3
- "bundledAt": "2026-03-11T16:21:41.120Z",
4
- "bundledFrom": "9678bf1"
2
+ "frameworkVersion": "1.0.8",
3
+ "bundledAt": "2026-03-11T17:33:39.633Z",
4
+ "bundledFrom": "66dd874"
5
5
  }
@@ -14,6 +14,10 @@ set -euo pipefail
14
14
  # ./launch-bugfix-daemon.sh logs [--lines N] [--follow]
15
15
  # ./launch-bugfix-daemon.sh restart [bug-fix-list.json] [--env "KEY=VAL ..."]
16
16
  #
17
+ # NOTE:
18
+ # In AI skill sessions, always use this daemon wrapper.
19
+ # Do NOT call `run-bugfix.sh run ...` directly, because foreground sessions may be killed by CLI timeout.
20
+ #
17
21
  # Files managed:
18
22
  # bugfix-state/.pipeline.pid - PID of the background run-bugfix.sh process
19
23
  # bugfix-state/pipeline-daemon.log - Consolidated stdout+stderr
@@ -14,6 +14,10 @@ set -euo pipefail
14
14
  # ./launch-daemon.sh logs [--lines N] [--follow]
15
15
  # ./launch-daemon.sh restart [feature-list.json] [--env "KEY=VAL ..."]
16
16
  #
17
+ # NOTE:
18
+ # In AI skill sessions, always use this daemon wrapper.
19
+ # Do NOT call `run.sh run ...` directly, because foreground sessions may be killed by CLI timeout.
20
+ #
17
21
  # Files managed:
18
22
  # state/.pipeline.pid - PID of the background run.sh process
19
23
  # state/pipeline-daemon.log - Consolidated stdout+stderr from run.sh
@@ -7,6 +7,12 @@ description: "Launch and manage the bugfix pipeline from within a cbc session. S
7
7
 
8
8
  Launch the autonomous bug fix pipeline from within a cbc conversation. The pipeline runs as a fully detached background process -- closing the cbc session does NOT stop the pipeline.
9
9
 
10
+ ### Mandatory Execution Mode (MUST)
11
+
12
+ - Always use daemon mode via `dev-pipeline/launch-bugfix-daemon.sh` for start/stop/status/log actions.
13
+ - NEVER run `dev-pipeline/run-bugfix.sh run ...` directly from this skill.
14
+ - Reason: foreground `run-bugfix.sh` can be terminated by AI CLI command timeout (e.g. cbc 120s), while daemon mode survives session timeout.
15
+
10
16
  ### When to Use
11
17
 
12
18
  **Start bugfix pipeline** -- User says:
@@ -14,7 +20,7 @@ Launch the autonomous bug fix pipeline from within a cbc conversation. The pipel
14
20
  - "start bug fix", "run bug fix", "execute bug list", "begin fixing"
15
21
  - "启动 bug 修复", "开始修复 bug", "运行 bug 修复流水线", "开始修 bug"
16
22
  - "修复所有 bug", "批量修复", "启动修复流水线"
17
- - After bug-planner completes: "go", "start", "fix them", "开始吧", "开始修复"
23
+ - After bug-planner completes: "fix them", "开始修复"
18
24
 
19
25
  **Check status** -- User says:
20
26
  - "bugfix status", "check bug fixes", "how's the fixing going", "bug fix progress"
@@ -7,6 +7,12 @@ description: "Launch and manage the dev-pipeline from within a cbc session. Star
7
7
 
8
8
  Launch the autonomous development pipeline from within a cbc conversation. The pipeline runs as a fully detached background process -- closing the cbc session does NOT stop the pipeline.
9
9
 
10
+ ### Mandatory Execution Mode (MUST)
11
+
12
+ - Always use daemon mode via `dev-pipeline/launch-daemon.sh` for start/stop/status/log actions.
13
+ - NEVER run `dev-pipeline/run.sh run ...` directly from this skill.
14
+ - Reason: foreground `run.sh` can be terminated by AI CLI command timeout (e.g. cbc 120s), while daemon mode survives session timeout.
15
+
10
16
  ### When to Use
11
17
 
12
18
  **Start pipeline** -- User says:
@@ -14,7 +20,7 @@ Launch the autonomous development pipeline from within a cbc conversation. The p
14
20
  - "run the features", "execute feature list", "start implementing"
15
21
  - "启动流水线", "开始实现", "运行流水线", "开始自动开发"
16
22
  - "实现接下来的步骤", "执行 feature list", "开始构建"
17
- - After app-planner completes: "go", "start", "build it", "开始吧"
23
+ - After app-planner completes: "build it", " feature list 开始开发"
18
24
 
19
25
  **Check status** -- User says:
20
26
  - "pipeline status", "check pipeline", "how's it going", "progress"
@@ -28,6 +34,10 @@ Launch the autonomous development pipeline from within a cbc conversation. The p
28
34
  - "show logs", "pipeline logs", "tail logs", "what's happening"
29
35
  - "查看日志", "流水线日志", "看看日志"
30
36
 
37
+ **Retry single feature node** -- User says:
38
+ - "retry F-003", "retry this feature", "retry this node"
39
+ - "重试 F-003", "重试这个节点", "重跑这个 feature"
40
+
31
41
  **Do NOT use this skill when:**
32
42
  - User wants to plan features (use `app-planner` instead)
33
43
  - User wants to implement a single feature manually within current session (use `prizmkit-implement`)
@@ -201,6 +211,26 @@ Pass via `--env`:
201
211
  dev-pipeline/launch-daemon.sh start feature-list.json --env "SESSION_TIMEOUT=7200 MAX_RETRIES=5 VERBOSE=1"
202
212
  ```
203
213
 
214
+ ---
215
+
216
+ #### Intent F: Retry Single Feature Node
217
+
218
+ When user says "retry F-003" or "重试 F-003":
219
+
220
+ ```bash
221
+ dev-pipeline/retry-feature.sh F-003 feature-list.json
222
+ ```
223
+
224
+ When user says "从头重试 F-003" or "clean retry F-003":
225
+
226
+ ```bash
227
+ dev-pipeline/reset-feature.sh F-003 --clean --run feature-list.json
228
+ ```
229
+
230
+ Notes:
231
+ - `retry-feature.sh` runs exactly one feature session and exits.
232
+ - Keep pipeline daemon mode for main run management (`launch-daemon.sh`).
233
+
204
234
  ### Error Handling
205
235
 
206
236
  | Error | Action |
@@ -211,7 +241,7 @@ dev-pipeline/launch-daemon.sh start feature-list.json --env "SESSION_TIMEOUT=720
211
241
  | Pipeline already running | Show status, ask if user wants to stop and restart |
212
242
  | PID file stale (process dead) | `launch-daemon.sh` auto-cleans, retry start |
213
243
  | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 dev-pipeline/state/pipeline-daemon.log` |
214
- | All features blocked/failed | Show status, suggest resetting failed features: `dev-pipeline/run.sh run <F-XXX> --clean` |
244
+ | All features blocked/failed | Show status, suggest daemon-safe recovery: `dev-pipeline/reset-feature.sh <F-XXX> --clean --run feature-list.json` |
215
245
  | Permission denied on script | Run `chmod +x dev-pipeline/launch-daemon.sh dev-pipeline/run.sh` |
216
246
 
217
247
  ### Integration Notes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.0.7",
3
+ "version": "1.0.8",
4
4
  "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
5
5
  "type": "module",
6
6
  "bin": {