prizmkit 1.1.99 → 1.1.101

package/bundled/skills/_metadata.json

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

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

@@ -11,8 +11,8 @@ Launch the autonomous bug fix pipeline from within an AI CLI conversation. Suppo
 
 Three execution modes are available. The user chooses one before configuring other options:
 
-1. **Foreground** (recommended) — `.prizmkit/dev-pipeline/run-bugfix.sh run`. Visible output, direct error feedback, no orphaned processes.
-2. **Background daemon** — `.prizmkit/dev-pipeline/launch-bugfix-daemon.sh`. Runs fully detached, survives AI CLI session closure.
+1. **Foreground** (recommended) — `python3 ./.prizmkit/dev-pipeline/cli.py bugfix run`. Visible output, direct error feedback, no orphaned processes.
+2. **Background daemon** — `python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json`. Runs fully detached, survives AI CLI session closure.
 3. **Manual** — Display the assembled command(s) only. Do not execute anything. User runs them on their own.
 
 **Background mode documentation**: When the user chooses background/daemon mode, record the choice and PID in `.prizmkit/bugfix-pipeline-run.log` (append-only) with timestamp, so the decision is traceable:
@@ -47,14 +47,15 @@ Three execution modes are available. The user chooses one before configuring oth
 
 Before any action, validate:
 
-1. **bugfix pipeline exists**: Confirm `.prizmkit/dev-pipeline/launch-bugfix-daemon.sh` and `.prizmkit/dev-pipeline/run-bugfix.sh` are present and executable
+1. **bugfix pipeline exists**: Confirm `.prizmkit/dev-pipeline/cli.py` is present
 2. **For start**: `.prizmkit/plans/bug-fix-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
-3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
-4. **Browser tools** (optional): If any bug has `browser_interaction` field, check the corresponding tool is available. Bugs may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
+3. **Dependencies**: `python3`, `git`, and AI CLI (`cbc` or `claude`) must be in PATH
+4. **Python version**: Requires Python 3.10+ for the unified dev-pipeline runtime
+5. **Browser tools** (optional): If any bug has `browser_interaction` field, check the corresponding tool is available. Bugs may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
 
 Quick check:
 ```bash
-command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
+command -v python3 && command -v git && (command -v cbc || command -v claude) && echo "All dependencies OK"
 # Optional: browser interaction support (check both tools — bugs may use either)
 command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (playwright browser verification will be skipped)"
 command -v opencli && echo "opencli OK" || echo "opencli not found (opencli browser verification will be skipped)"
@@ -80,7 +81,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **Check not already running**:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix status 2>/dev/null
    ```
    If running, inform user and ask: "Bugfix pipeline is already running. Want to restart it, check status, or view logs?"
 
@@ -106,10 +107,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    If pipeline state already exists, use the status command instead:
    ```bash
-   python3 .prizmkit/dev-pipeline/scripts/update-bug-status.py \
-     --bug-list .prizmkit/plans/bug-fix-list.json \
-     --state-dir .prizmkit/state/bugfix \
-     --action status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py bugfix status .prizmkit/plans/bug-fix-list.json
    ```
 
 4. **Ask execution mode** (first user decision — SEPARATE `AskUserQuestion` call with exactly 1 question):
@@ -125,34 +123,34 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 .prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
+   VERBOSE=1 python3 ./.prizmkit/dev-pipeline/cli.py bugfix run .prizmkit/plans/bug-fix-list.json
    ```
    With all options:
    ```bash
    VERBOSE=1 MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
-     .prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
+     python3 ./.prizmkit/dev-pipeline/cli.py bugfix run .prizmkit/plans/bug-fix-list.json
    ```
 
    **Background daemon command:**
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json --env "VERBOSE=1"
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json --env "VERBOSE=1"
    ```
    With all options:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json \
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json \
      --env "VERBOSE=1 MAX_RETRIES=5 ENABLE_DEPLOY=1"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 7.
    ```
    # To run in foreground:
-   VERBOSE=1 .prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
+   VERBOSE=1 python3 ./.prizmkit/dev-pipeline/cli.py bugfix run .prizmkit/plans/bug-fix-list.json
 
    # To run in background (detached):
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json --env "VERBOSE=1"
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json --env "VERBOSE=1"
 
    # To check status:
-   .prizmkit/dev-pipeline/run-bugfix.sh status .prizmkit/plans/bug-fix-list.json
+   python3 ./.prizmkit/dev-pipeline/cli.py bugfix status .prizmkit/plans/bug-fix-list.json
    ```
 
 7. **Confirm and launch** (Foreground and Background only — Manual mode ends at step 6):
@@ -166,16 +164,16 @@ Detect user intent from their message, then follow the corresponding workflow:
    **If foreground**: Pipeline runs to completion in the terminal. After it finishes:
    - Summarize results: total bugs, fixed, failed, skipped
    - If all fixed: each bug session has already run `prizmkit-retrospective` internally (structural sync by default; full retrospective when the fix changed interfaces, dependencies, or observable behavior). Ask user what's next.
-   - If some failed: show failed bug IDs and suggest `.prizmkit/dev-pipeline/reset-bug.sh <B-XXX> --clean --run` for a fresh retry
+   - If some failed: show failed bug IDs and suggest `python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix <B-XXX> --clean --run` for a fresh retry
 
    **If background daemon**:
    1. Verify launch:
       ```bash
-      .prizmkit/dev-pipeline/launch-bugfix-daemon.sh status
+      python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix status
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
-      tail -f .prizmkit/state/bugfix/pipeline-daemon.log
+      python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix logs --follow
       ```
    3. Report to user:
       - Pipeline PID
@@ -189,20 +187,17 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check daemon status**:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh status
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix status
    ```
 
 2. **Show bug-level progress**:
    ```bash
-   python3 .prizmkit/dev-pipeline/scripts/update-bug-status.py \
-     --bug-list .prizmkit/plans/bug-fix-list.json \
-     --state-dir .prizmkit/state/bugfix \
-     --action status
+   python3 ./.prizmkit/dev-pipeline/cli.py bugfix status .prizmkit/plans/bug-fix-list.json
    ```
 
 3. **Show recent log activity** (last 20 lines):
    ```bash
-   tail -20 .prizmkit/state/bugfix/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix logs --lines 20
    ```
 
 4. **Summarize** to user: total bugs, completed, in-progress, failed, pending, needs-info.
@@ -213,12 +208,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Stop the daemon**:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh stop
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix stop
    ```
 
 2. **Verify stopped**:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null || true
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix status 2>/dev/null || true
    ```
 
 3. **Inform user**: "Bugfix pipeline stopped. State is preserved -- you can resume later with 'start bug fix' and it will pick up where it left off."
@@ -229,17 +224,17 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check if running**:
    ```bash
-   .prizmkit/dev-pipeline/launch-bugfix-daemon.sh status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix status 2>/dev/null
    ```
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
    ```bash
-   tail -f .prizmkit/state/bugfix/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix logs --follow
    ```
 
 3. **If not running** -- Show last 50 lines:
    ```bash
-   tail -50 .prizmkit/state/bugfix/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix logs --lines 50
    ```
 
 4. **For per-bug session logs** (when user asks about a specific bug):
@@ -257,10 +252,10 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry B-001":
 
 ```bash
-.prizmkit/dev-pipeline/reset-bug.sh B-001 --clean --run .prizmkit/plans/bug-fix-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix B-001 --clean --run .prizmkit/plans/bug-fix-list.json
 ```
 
-**Note:** `reset-bug.sh --clean --run` performs a full clean (deletes session history and artifacts) before retrying — this gives a fresh start.
+**Note:** `python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix <B-XXX> --clean --run .prizmkit/plans/bug-fix-list.json` performs a full clean (deletes session history and artifacts) before retrying the selected bug — this gives a fresh start.
 
 ### Error Handling
 

package/bundled/skills/bugfix-pipeline-launcher/references/configuration.md

@@ -76,13 +76,14 @@ Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off
 | Error | Action |
 |-------|--------|
 | `.prizmkit/plans/bug-fix-list.json` not found | Tell user to run `bug-planner` skill first |
-| `jq` not installed | Suggest: `brew install jq` |
+| `python3` not installed | Install Python 3.10+ and rerun the Python runtime command |
+| `git` not installed | Install git; the Python runtime uses git for branch/worktree/status operations |
 | `cbc`/`claude` not in PATH | Check AI CLI installation |
 | Bugfix pipeline already running | Show status, ask if user wants to stop and restart |
-| PID file stale (process dead) | `launch-bugfix-daemon.sh` auto-cleans, retry start |
-| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/bugfix/pipeline-daemon.log` |
-| All bugs blocked/failed/needs-info | Show status, suggest retrying or providing more info |
+| PID file stale (process dead) | `python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix start .prizmkit/plans/bug-fix-list.json` auto-cleans, retry start |
+| Launch failed (process died immediately) | Show last 20 lines of log: `python3 ./.prizmkit/dev-pipeline/cli.py daemon bugfix logs --lines 20` |
+| All bugs blocked/failed/needs-info | Show status, suggest retrying with `python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix <B-XXX> --clean --run .prizmkit/plans/bug-fix-list.json` or providing more info |
 | `playwright-cli` not installed | Browser verification skipped for playwright bugs (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
 | `opencli` not installed | Browser verification skipped for opencli bugs (non-blocking). Install opencli for Chrome session-based browser verification |
 | Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/bugfix/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
-| Permission denied on script | Run `chmod +x .prizmkit/dev-pipeline/launch-bugfix-daemon.sh .prizmkit/dev-pipeline/run-bugfix.sh` |
+| Permission denied running Python CLI | Ensure Python is installed and the command uses `python3 ./.prizmkit/dev-pipeline/cli.py ...` |

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

@@ -38,15 +38,15 @@ Three execution modes are available (Foreground / Background daemon / Manual); t
 
 Before any action, validate:
 
-1. **dev-pipeline exists**: Confirm `.prizmkit/dev-pipeline/launch-feature-daemon.sh` is present and executable
+1. **dev-pipeline exists**: Confirm `.prizmkit/dev-pipeline/cli.py` is present
 2. **For start**: `.prizmkit/plans/feature-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
-3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
-4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
+3. **Dependencies**: `python3`, `git`, and AI CLI (`cbc` or `claude`) must be in PATH
+4. **Python version**: Requires Python 3.10+ for the unified dev-pipeline runtime
 5. **Browser tools** (optional): If any feature has `browser_interaction` field, check the corresponding tool is available. Features may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
 
 Quick check:
 ```bash
-command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
+command -v python3 && command -v git && (command -v cbc || command -v claude) && echo "All dependencies OK"
 # Optional: browser interaction support (check both tools — features may use either)
 command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (playwright browser verification will be skipped)"
 command -v opencli && echo "opencli OK" || echo "opencli not found (opencli browser verification will be skipped)"
@@ -72,7 +72,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **Check not already running**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status 2>/dev/null
    ```
    If running, inform user and ask: "Pipeline is already running. Want to restart it, check status, or view logs?"
 
@@ -90,10 +90,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    If pipeline state already exists, use the status command instead:
    ```bash
-   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
-     --feature-list .prizmkit/plans/feature-list.json \
-     --state-dir .prizmkit/state/features \
-     --action status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py feature status .prizmkit/plans/feature-list.json
    ```
 
 4. **Run environment preflight checks** (database connectivity, migrations, dev server):
@@ -126,8 +123,8 @@ Detect user intent from their message, then follow the corresponding workflow:
    Use `AskUserQuestion` with exactly 1 question:
 
    **Question 1 — Execution mode** (multiSelect: false):
-   - Foreground (Recommended) — pipeline runs in the current session via `run-feature.sh run`. Visible output and direct error feedback.
-   - Background daemon — pipeline runs fully detached via `launch-feature-daemon.sh`. Survives AI CLI session closure.
+   - Foreground (Recommended) — pipeline runs in the current session via `python3 ./.prizmkit/dev-pipeline/cli.py feature run`. Visible output and direct error feedback.
+   - Background daemon — pipeline runs fully detached via `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json`. Survives AI CLI session closure.
    - Manual — display the final assembled commands only. Do not execute anything. User runs them on their own.
 
    STOP HERE and wait for user response before continuing to step 6.
@@ -164,34 +161,34 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 .prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+   VERBOSE=1 python3 ./.prizmkit/dev-pipeline/cli.py feature run .prizmkit/plans/feature-list.json
    ```
    With all options:
    ```bash
    VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
-     .prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --features F-001:F-005
+     python3 ./.prizmkit/dev-pipeline/cli.py feature run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 
    **Background daemon command:**
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
    ```
    With all options:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --features F-001:F-005 \
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json --features F-001:F-005 \
      --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.
    ```
    # To run in foreground:
-   VERBOSE=1 .prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+   VERBOSE=1 python3 ./.prizmkit/dev-pipeline/cli.py feature run .prizmkit/plans/feature-list.json
 
    # To run in background (detached):
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json --env "VERBOSE=1"
 
    # To check status:
-   .prizmkit/dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
+   python3 ./.prizmkit/dev-pipeline/cli.py feature status .prizmkit/plans/feature-list.json
    ```
 
 8. **Confirm and launch** (Foreground and Background only — Manual mode ends at step 7):
@@ -205,17 +202,17 @@ Detect user intent from their message, then follow the corresponding workflow:
    **If foreground**: Pipeline runs to completion in the terminal. After it finishes:
    - Summarize results: total features, succeeded, failed, skipped
    - If all succeeded: each feature session has already run `prizmkit-retrospective` internally. Ask user what's next.
-   - If some failed: show failed feature IDs and suggest `reset-feature.sh <F-XXX> --clean --run` for a fresh retry
+   - If some failed: show failed feature IDs and suggest `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run` for a fresh retry
    - **Browser verification**: If any completed features have `browser_interaction` and the corresponding browser tool (`playwright-cli` or `opencli`) is installed, offer to run browser verification (see Post-Pipeline Browser Verification)
 
    **If background daemon**:
    1. Verify launch:
       ```bash
-      .prizmkit/dev-pipeline/launch-feature-daemon.sh status
+      python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
-      tail -f .prizmkit/state/features/pipeline-daemon.log
+      python3 ./.prizmkit/dev-pipeline/cli.py daemon feature logs --follow
       ```
    3. Report to user:
       - Pipeline PID
@@ -229,20 +226,17 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check daemon status**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh status
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status
    ```
 
 2. **Show feature-level progress**:
    ```bash
-   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
-     --feature-list .prizmkit/plans/feature-list.json \
-     --state-dir .prizmkit/state/features \
-     --action status
+   python3 ./.prizmkit/dev-pipeline/cli.py feature status .prizmkit/plans/feature-list.json
    ```
 
 3. **Show recent log activity** (last 20 lines):
    ```bash
-   tail -20 .prizmkit/state/features/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature logs --lines 20
    ```
 
 4. **Summarize** to user: total features, completed, in-progress, failed, pending.
@@ -253,12 +247,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Stop the daemon**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh stop
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature stop
    ```
 
 2. **Verify stopped**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh status 2>/dev/null || true
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status 2>/dev/null || true
    ```
 
 3. **Inform user**: "Pipeline stopped. State is preserved -- you can resume later with 'start pipeline' and it will pick up where it left off."
@@ -269,17 +263,17 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check if running**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status 2>/dev/null
    ```
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
    ```bash
-   tail -f .prizmkit/state/features/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature logs --follow
    ```
 
 3. **If not running** -- Show last 50 lines:
    ```bash
-   tail -50 .prizmkit/state/features/pipeline-daemon.log
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature logs --lines 50
    ```
 
 4. **For per-feature session logs** (when user asks about a specific feature):
@@ -297,12 +291,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry F-003" or "clean retry F-003":
 
 ```bash
-.prizmkit/dev-pipeline/reset-feature.sh F-003 --clean --run .prizmkit/plans/feature-list.json
+python3 ./.prizmkit/dev-pipeline/cli.py reset feature F-003 --clean --run .prizmkit/plans/feature-list.json
 ```
 
 Notes:
-- `reset-feature.sh --clean --run` performs a full clean (deletes session history and artifacts) before retrying — this gives a fresh start.
-- Keep pipeline daemon mode for main run management (`launch-feature-daemon.sh`).
+- `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run .prizmkit/plans/feature-list.json` performs a full clean (deletes session history and artifacts) before retrying the selected feature — this gives a fresh start.
+- Keep pipeline daemon mode for main run management (`python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start`, `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status`, or `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature stop`).
 
 ---
 

package/bundled/skills/feature-pipeline-launcher/references/configuration.md

@@ -54,16 +54,17 @@ Not exposed in interactive menu, pass via `--env`:
 | Error | Action |
 |-------|--------|
 | `.prizmkit/plans/feature-list.json` not found | Tell user to run `feature-planner` skill first |
-| `jq` not installed | Suggest: `brew install jq` |
+| `python3` not installed | Install Python 3.10+ and rerun the Python runtime command |
+| `git` not installed | Install git; the Python runtime uses git for branch/worktree/status operations |
 | `cbc`/`claude` not in PATH | Check AI CLI installation |
 | Pipeline already running | Show status, ask if user wants to stop and restart |
-| PID file stale (process dead) | `launch-feature-daemon.sh` auto-cleans, retry start |
-| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/features/pipeline-daemon.log` |
-| Feature stuck/blocked | Use `reset-feature.sh <F-XXX> --clean --run` for a fresh retry |
-| All features blocked/failed | Show status, suggest daemon-safe recovery: `.prizmkit/dev-pipeline/reset-feature.sh <F-XXX> --clean --run .prizmkit/plans/feature-list.json` |
+| PID file stale (process dead) | `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json` auto-cleans, retry start |
+| Launch failed (process died immediately) | Show last 20 lines of log: `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature logs --lines 20` |
+| Feature stuck/blocked | Use `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run` for a fresh retry |
+| All features blocked/failed | Show status, suggest daemon-safe recovery: `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run .prizmkit/plans/feature-list.json` |
 | `playwright-cli` not installed | Browser verification skipped for playwright features (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
 | `opencli` not installed | Browser verification skipped for opencli features (non-blocking). Install opencli for Chrome session-based browser verification |
-| Permission denied on script | Run `chmod +x .prizmkit/dev-pipeline/launch-feature-daemon.sh .prizmkit/dev-pipeline/run-feature.sh` |
+| Permission denied running Python CLI | Ensure Python is installed and the command uses `python3 ./.prizmkit/dev-pipeline/cli.py ...` |
 | Pipeline stop failed (process won't die) | Process may be stuck in I/O wait. Try `kill -9 <PID>` manually. Check for orphaned child processes with `ps aux \| grep claude` |
 | Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/features/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
 | `.env.local` missing or incomplete | Warn: database connection variables not found. Suggest creating env file with required connection variables for the project's database |

package/bundled/skills/feature-workflow/SKILL.md

@@ -245,7 +245,7 @@ Never proceed without explicit user confirmation via `AskUserQuestion`. Do NOT r
 
 1. **Initial status check**:
    ```bash
-   .prizmkit/dev-pipeline/launch-feature-daemon.sh status
+   python3 ./.prizmkit/dev-pipeline/cli.py daemon feature status
    ```
 
 2. **Offer monitoring options**:
@@ -255,10 +255,7 @@ Never proceed without explicit user confirmation via `AskUserQuestion`. Do NOT r
 
 3. **Periodic progress reports** (when user asks):
    ```bash
-   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
-     --feature-list .prizmkit/plans/feature-list.json \
-     --state-dir .prizmkit/state/features \
-     --action status
+   python3 ./.prizmkit/dev-pipeline/cli.py feature status .prizmkit/plans/feature-list.json
    ```
 
 4. **Completion report** (when pipeline finishes all features):
@@ -316,7 +313,7 @@ While the pipeline runs, the user can continue the conversation:
 | Brainstorming stalls | Offer concrete options: "Would you prefer A or B?" |
 | `feature-planner` cannot parse requirements | Refine the requirements summary and retry |
 | `.prizmkit/plans/feature-list.json` generation failed | Show error, retry with refined input |
-| Pipeline launch failed | Show daemon log, suggest manual start |
+| Pipeline launch failed | Show daemon log, suggest manual start with `python3 ./.prizmkit/dev-pipeline/cli.py feature run .prizmkit/plans/feature-list.json` or `python3 ./.prizmkit/dev-pipeline/cli.py daemon feature start .prizmkit/plans/feature-list.json` |
 | All features blocked/failed | Show status, suggest retrying specific features |
 | User wants to cancel mid-brainstorming | Save conversation context, offer to resume later |
 

package/bundled/skills/recovery-workflow/SKILL.md

@@ -16,32 +16,32 @@ User says:
 - "Don't want to restart from scratch"
 
 **Do NOT use when:**
-- Pipeline interrupted → use `reset-feature.sh --clean --run` / `reset-bug.sh --clean --run` for a fresh retry
+- Pipeline interrupted → use `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run .prizmkit/plans/feature-list.json` / `python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix <B-XXX> --clean --run .prizmkit/plans/bug-fix-list.json` for a fresh retry
 - User wants a clean restart → use the original workflow skill directly (`/feature-workflow`, `/bug-fix-workflow`, `/refactor-workflow`)
 - Nothing was ever started → use the original workflow skill
 
 ## Pipeline Recovery (Recommended)
 
-**IMPORTANT**: In Phase 1.3, you MUST present the user with a choice between pipeline recovery (`run-recovery.sh`) and interactive recovery. **NEVER skip this choice. NEVER decide for the user.** The pipeline approach is recommended because it generates a comprehensive bootstrap prompt that explicitly lists every remaining phase with full instructions, ensuring the AI completes the full workflow — not just the implementation part.
+**IMPORTANT**: In Phase 1.3, you MUST present the user with a choice between pipeline recovery (`python3 ./.prizmkit/dev-pipeline/cli.py recovery run`) and interactive recovery. **NEVER skip this choice. NEVER decide for the user.** The pipeline approach is recommended because it generates a comprehensive bootstrap prompt that explicitly lists every remaining phase with full instructions, ensuring the AI completes the full workflow — not just the implementation part.
 
 Pipeline commands (for reference — Phase 1.3 will present these as a selectable option):
 
 ```bash
-./.prizmkit/dev-pipeline/run-recovery.sh                    # Auto-detect and recover
-./.prizmkit/dev-pipeline/run-recovery.sh detect              # Detection report only
-./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
-./.prizmkit/dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
-./.prizmkit/dev-pipeline/run-recovery.sh run --model <model> # Override AI model
+python3 ./.prizmkit/dev-pipeline/cli.py recovery run                # Auto-detect and recover
+python3 ./.prizmkit/dev-pipeline/cli.py recovery detect              # Detection report only
+python3 ./.prizmkit/dev-pipeline/cli.py recovery run --dry-run       # Generate prompt, don't execute
+python3 ./.prizmkit/dev-pipeline/cli.py recovery run --yes           # Skip confirmation
+python3 ./.prizmkit/dev-pipeline/cli.py recovery run --model <model> # Override AI model
 ```
 
 ### When to use pipeline vs interactive recovery
 
 | Scenario | Approach |
 |----------|----------|
-| Pipeline session timed out / crashed | `./run-recovery.sh` — autonomous, completes all phases reliably |
+| Pipeline session timed out / crashed | `python3 ./.prizmkit/dev-pipeline/cli.py recovery run` — autonomous, completes all phases reliably |
 | Interactive session interrupted | This skill (`/recovery-workflow`) — for in-session interactive use |
-| Want to inspect before recovering | `./run-recovery.sh detect` or `./run-recovery.sh run --dry-run` |
-| Daemon/scripted use | `./run-recovery.sh run --yes` — no user confirmation needed |
+| Want to inspect before recovering | `python3 ./.prizmkit/dev-pipeline/cli.py recovery detect` or `python3 ./.prizmkit/dev-pipeline/cli.py recovery run --dry-run` |
+| Daemon/scripted use | `python3 ./.prizmkit/dev-pipeline/cli.py recovery run --yes` — no user confirmation needed |
 
 ## Supported Workflows
 
@@ -68,7 +68,7 @@ Pipeline commands (for reference — Phase 1.3 will present these as a selectabl
    4. Display diagnosis + detection results
    5. If code changes exist → run test suite
    6. If multiple failed tasks → ask user which to recover
-   7. User chooses: run-recovery.sh (recommended) | interactive | start fresh
+   7. User chooses: python3 ./.prizmkit/dev-pipeline/cli.py recovery run (recommended) | interactive | start fresh
 3. **Phase 2: Execute remaining steps**
    1. Read target workflow's SKILL.md
    2. Read existing artifacts to restore context
@@ -106,22 +106,13 @@ Before showing the recovery report, run a comprehensive diagnosis:
 2. **Scan all pipelines for failed/in-progress tasks**:
    ```bash
    # Feature pipeline
-   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
-     --feature-list .prizmkit/plans/feature-list.json \
-     --state-dir .prizmkit/state/features \
-     --action status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py feature status .prizmkit/plans/feature-list.json
 
    # Bugfix pipeline
-   python3 .prizmkit/dev-pipeline/scripts/update-bug-status.py \
-     --bug-list .prizmkit/plans/bug-fix-list.json \
-     --state-dir .prizmkit/state/bugfix \
-     --action status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py bugfix status .prizmkit/plans/bug-fix-list.json
 
    # Refactor pipeline
-   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
-     --refactor-list .prizmkit/plans/refactor-list.json \
-     --state-dir .prizmkit/state/refactor \
-     --action status 2>/dev/null
+   python3 ./.prizmkit/dev-pipeline/cli.py refactor status .prizmkit/plans/refactor-list.json
    ```
    For each pipeline that has state, extract: total tasks, completed, failed, in-progress, pending.
 
@@ -224,7 +215,7 @@ AskUserQuestion:
   header: "Recovery"
   options:
     - label: "Run recovery script (Recommended)"
-      description: "Execute ./.prizmkit/dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
+      description: "Execute python3 ./.prizmkit/dev-pipeline/cli.py recovery run — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
     - label: "Copy command and run manually"
       description: "I'll give you the exact shell command to paste into your terminal — you run it yourself outside this session"
     - label: "Resume interactively in this session"
@@ -235,7 +226,7 @@ AskUserQuestion:
 
 **If "Run recovery script"** → Execute the pipeline recovery:
 ```bash
-./.prizmkit/dev-pipeline/run-recovery.sh
+python3 ./.prizmkit/dev-pipeline/cli.py recovery run
 ```
 The script handles everything: detection, confirmation, prompt generation, session spawn, and post-session validation. **End this skill after launching the script** — do not proceed to Phase 2.
 
@@ -243,12 +234,12 @@ The script handles everything: detection, confirmation, prompt generation, sessi
 ```
 To recover, run this command in your project root:
 
-  ./.prizmkit/dev-pipeline/run-recovery.sh
+  python3 ./.prizmkit/dev-pipeline/cli.py recovery run
 
 Or with options:
-  ./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
-  ./.prizmkit/dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
-  ./.prizmkit/dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
+  python3 ./.prizmkit/dev-pipeline/cli.py recovery run --dry-run    # Preview the recovery prompt first
+  python3 ./.prizmkit/dev-pipeline/cli.py recovery run --yes         # Skip confirmation
+  python3 ./.prizmkit/dev-pipeline/cli.py recovery run --model <model>  # Specify AI model
 ```
 **End this skill** — do not proceed to Phase 2. The user will run the command themselves.
 
@@ -339,9 +330,9 @@ Recovery complete.
 | `bug-fix-workflow` | **Recovery target** — this skill can resume interrupted bug-fix-workflow sessions |
 | `refactor-workflow` | **Recovery target** — this skill can resume interrupted refactor-workflow sessions |
 | `feature-pipeline-launcher` | **Called in Phase 2.2** — launches or checks pipeline status for feature recovery |
-| `reset-feature.sh --clean --run` | **Alternative** — full clean retry for pipeline failures; this skill is the smart interactive alternative |
-| `reset-bug.sh --clean --run` | **Alternative** — full clean retry for bugfix pipeline failures |
-| `run-recovery.sh` | **Pipeline counterpart** — shell-driven recovery that generates bootstrap prompt and spawns AI CLI session for autonomous completion |
+| `python3 ./.prizmkit/dev-pipeline/cli.py reset feature <F-XXX> --clean --run .prizmkit/plans/feature-list.json` | **Alternative** — full clean retry for pipeline failures; this skill is the smart interactive alternative |
+| `python3 ./.prizmkit/dev-pipeline/cli.py reset bugfix <B-XXX> --clean --run .prizmkit/plans/bug-fix-list.json` | **Alternative** — full clean retry for bugfix pipeline failures |
+| `python3 ./.prizmkit/dev-pipeline/cli.py recovery run` | **Pipeline counterpart** — Python recovery that generates bootstrap prompt and spawns AI CLI session for autonomous completion |
 | `/prizmkit-code-review` | **Called in Phase 2.1** — reviews recovered bug-fix code |
 | `/prizmkit-committer` | **Called in Phase 2.1** — commits the recovered result |