prizmkit 1.1.79 → 1.1.81

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

@@ -0,0 +1,94 @@
+# Configuration Reference — Bugfix Pipeline Launcher (Windows)
+
+Environment variable mappings for the bugfix launcher.
+
+## Environment Variable Mapping
+
+Translating user responses to env vars:
+
+| Config choice | Environment variable |
+|-----------|---------------------|
+| Verbose: Off | `VERBOSE=0` |
+| Verbose: On | `VERBOSE=1` |
+| Max retries: N | `MAX_RETRIES=N` |
+| Critic: On | `ENABLE_CRITIC=1` |
+| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
+| Stop on failure: On | `STOP_ON_FAILURE=1` |
+| Deploy: Yes | `ENABLE_DEPLOY=1` |
+| Effort: value | `PRIZMKIT_EFFORT=<value>` |
+
+## Advanced Environment Variables
+
+Not exposed in interactive menu, pass via `--env`:
+
+| Variable | Default | Purpose |
+|----------|---------|---------|
+| `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
+| `AUTO_PUSH` | `0` | Auto-push to remote after successful bug fix (`1` to enable) |
+| `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `bugfix/pipeline-{run_id}`) |
+| `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
+| `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
+| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
+| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
+| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
+
+## Interactive Configuration Options
+
+Present these via `AskUserQuestion` in step 5. Round 1 is one `AskUserQuestion` call with all 4 questions; round 2 only runs if the user picks "Yes" to Advanced config.
+
+### Round 1 (always asked)
+
+**Question 1 — Verbose logging** (multiSelect: false):
+- On (default) — Detailed AI session logs including tool calls and subagent activity
+- Off — Minimal logging
+
+**Question 2 — Max retries** (multiSelect: false):
+- 3 (default)
+- 1
+- 5
+
+**Question 3 — Critic review** (multiSelect: false):
+- Off (default) — Skip adversarial review (`ENABLE_CRITIC=0`)
+- On — Enable adversarial critic review (`ENABLE_CRITIC=1`): an independent AI agent reviews the diagnosis/plan for completeness and the fix for defects, edge cases, and regression risks. Adds ~5-10 min per bug.
+
+**Question 4 — Advanced config?** (multiSelect: false):
+- No (default) — Use defaults for session timeout and failure behavior
+- Yes — Configure session timeout, stop-on-failure, and reasoning effort options
+
+Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
+
+### Round 2 (only if Advanced config = Yes)
+
+**Question 1 — Session timeout** (multiSelect: false):
+- None (default) — No timeout
+- 30 min — `SESSION_TIMEOUT=1800`
+- 1 hour — `SESSION_TIMEOUT=3600`
+- 2 hours — `SESSION_TIMEOUT=7200`
+
+**Question 2 — Stop on failure** (multiSelect: false):
+- Off (default) — Pipeline continues to next task after failure
+- On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
+
+**Question 3 — Reasoning effort** (multiSelect: false):
+- Default (none) — Use CLI default
+- low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+- medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+- high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+- xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+- max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| `.prizmkit/plans/bug-fix-list.json` not found | Tell user to run `bug-planner` skill first |
+| JSON parsing failed | Use the bundled Python validation/status scripts instead of external JSON tools |
+| AI CLI not in PATH | Check Codex (`codex`), Claude (`claude`), or CodeBuddy (`cbc`) installation |
+| Bugfix pipeline already running | Show status, ask if user wants to stop and restart |
+| PID file stale (process dead) | `launch-bugfix-daemon.ps1` auto-cleans, retry start |
+| Launch failed (process died immediately) | Show last 20 lines of log: `Get-Content -Tail 20 .prizmkit/state/daemon/bugfix-daemon.log` |
+| All bugs blocked/failed/needs-info | Show status, suggest retrying 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`. |
+| PowerShell execution policy blocks script | Run `Set-ExecutionPolicy -Scope Process Bypass` for the current terminal |

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

@@ -7,37 +7,27 @@ description: "Launch and manage the dev-pipeline from within an AI CLI session.
 
 Launch the autonomous development pipeline from within an AI CLI conversation. The pipeline runs as a fully detached background process -- closing the AI CLI session does NOT stop the pipeline.
 
-### Execution Mode
-
-Three execution modes are available. The user chooses one before configuring other options:
-
-1. **Foreground** (recommended) — `.\.prizmkit\dev-pipeline\run-feature.ps1 run`. Visible output, direct error feedback, no orphaned processes.
-2. **Background daemon** — `.\.prizmkit\dev-pipeline\launch-feature-daemon.ps1`. 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.
+Three execution modes are available (Foreground / Background daemon / Manual); they are defined authoritatively in **Intent A, step 5** below.
 
 ### When to Use
 
 **Start pipeline** -- User says:
-- "run pipeline", "start pipeline", "start building", "launch dev-pipeline"
-- "run the features", "execute feature list", "start implementing"
-- "launch pipeline", "run the pipeline", "start auto-development"
-- After feature-planner completes: "build it", "start developing from the feature list"
-- "run only F-001 to F-005", "run features F-001,F-003", "only build these features"
+- "run feature pipeline", "run pipeline", "start building features", "launch feature pipeline"
+- "start implementing", "execute feature list", "build all features"
+- After feature-planner completes: "build them", "start building from the list"
+- Supports running a feature subset (e.g. "run only F-001 to F-005", "run features F-001,F-003").
 
 **Check status** -- User says:
-- "pipeline status", "check pipeline", "how's it going", "progress"
-- "check progress", "what's the current situation"
+- "pipeline status", "feature progress", "check the pipeline", "how's the build going"
 
 **Stop pipeline** -- User says:
-- "stop pipeline", "kill pipeline", "halt", "pause"
-- "stop the pipeline", "pause the pipeline"
+- "stop pipeline", "stop the pipeline", "halt pipeline", "pause the build"
 
 **Show logs** -- User says:
-- "show logs", "pipeline logs", "tail logs", "what's happening"
-- "view logs", "check the logs"
+- "pipeline logs", "show pipeline logs", "what's building"
 
-**Retry single feature node** -- User says:
-- "retry F-003", "retry this feature", "retry this node", "re-run this feature"
+**Retry single feature** -- User says:
+- "retry F-001", "re-run F-001", "retry this feature"
 
 **Do NOT use this skill when:**
 - User wants to plan features (use `feature-planner` instead)
@@ -155,9 +145,9 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    If `global_context.database` is absent and no features mention database keywords, the script skips DB checks automatically.
 
-5. **Ask execution mode** (first user decision — SEPARATE `AskUserQuestion` call):
+5. **Ask execution mode** (first user decision):
 
-   ⛔ **This MUST be its own standalone `AskUserQuestion` call.** Do NOT combine execution mode with step 6 config questions. The execution mode question is asked ALONE, user responds, THEN you proceed to step 6.
+   **RULE: Ask step 5 and step 6 in separate `AskUserQuestion` calls.** Combining them makes the model merge the questions and skip the mode selection. Ask execution mode ALONE here, wait for the response, THEN proceed to step 6.
 
    Use `AskUserQuestion` with exactly 1 question:
 
@@ -166,19 +156,11 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Background daemon — pipeline runs fully detached via `launch-feature-daemon.ps1`. 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.
-
-6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). This is a SEPARATE `AskUserQuestion` call from step 5. You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7.
+   STOP HERE and wait for user response before continuing to step 6.
 
-   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response. You MUST NOT:
-   - Combine step 5 and step 6 into one `AskUserQuestion` call (this is the most common violation — execution mode MUST be asked separately in step 5)
-   - Skip this step and jump to step 7
-   - Merge step 6 and step 7 into one response
-   - Assume default values and show the command without asking
-   - Show the command as text and ask "ready?" without presenting the options
-   If you find yourself writing the final command before the user has answered these 4 questions, STOP — you are violating this rule.
+6. **Ask configuration options** — MANDATORY INTERACTIVE STEP, applies to ALL execution modes (Foreground, Background, AND Manual). This is a SEPARATE `AskUserQuestion` call from step 5 (see the RULE above). You MUST call `AskUserQuestion` with the 4 questions below and WAIT for the user's response before proceeding to step 7. Do NOT assume defaults, do NOT show the command as text and ask "ready?", and do NOT merge step 6 and step 7. If you find yourself writing the final command before the user has answered these 4 questions, STOP — you are violating this rule.
 
-   Use `AskUserQuestion` to present ALL 4 configuration choices (the full 4-question budget goes to config, NOT shared with execution mode):
+   Use `AskUserQuestion` to present ALL 4 configuration choices:
 
    **Question 1 — Critic review** (multiSelect: false):
    - Off (default) — Skip adversarial review
@@ -199,46 +181,11 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 
-   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion`:
-
-   **Question 1 — Session timeout** (multiSelect: false):
-   - None (default) — No timeout
-   - 30 min — `SESSION_TIMEOUT=1800`
-   - 1 hour — `SESSION_TIMEOUT=3600`
-   - 2 hours — `SESSION_TIMEOUT=7200`
-
-   **Question 2 — Stop on failure** (multiSelect: false):
-   - Off (default) — Pipeline continues to next task after failure
-   - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
-
-   **Question 3 — Reasoning effort** (multiSelect: false):
-   - Default (none) — Use CLI default
-   - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
-   - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
-   - high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
-   - xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
-   - max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
-
-   **Environment variable mapping** (for translating user responses → env vars):
-
-   | Config choice | Environment variable |
-   |-----------|---------------------|
-   | Critic: On | `ENABLE_CRITIC=true` |
-   | Verbose: Off | `VERBOSE=0` |
-   | Verbose: On | `VERBOSE=1` |
-   | Max retries: N | `MAX_RETRIES=N` |
-   | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
-   | Stop on failure: On | `STOP_ON_FAILURE=1` |
-   | Effort: value | `PRIZMKIT_EFFORT=<value>` |
-
-   **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion` — see the advanced config questions (session timeout, stop-on-failure, reasoning effort) in `${SKILL_DIR}/references/configuration.md`.
 
-   | Variable | Default | Purpose |
-   |----------|---------|---------|
-   | `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
-   | `PIPELINE_MODE` | (none) | Override mode for all features: `lite`\|`standard`\|`full` |
+   **Environment variable mapping** and **advanced environment variables** tables — read `${SKILL_DIR}/references/configuration.md` for the full translation tables (8 config→env mappings + 9 advanced variables).
 
-   ⚠️ STOP HERE and wait for user response before continuing to step 7.
+   STOP HERE and wait for user response before continuing to step 7.
 
 7. **Show final command**: After user confirms configuration in step 6, assemble the complete command from execution mode + user-confirmed configuration, and present it to the user.
 
@@ -422,23 +369,7 @@ After pipeline completion, if features have `browser_interaction` fields and the
 
 ### Error Handling
 
-| Error | Action |
-|-------|--------|
-| `.prizmkit/plans/feature-list.json` not found | Tell user to run `feature-planner` skill first |
-| JSON parsing failed | Use the bundled Python validation/status scripts instead of external JSON tools |
-| AI CLI not in PATH | Check Codex (`codex`), Claude (`claude`), or CodeBuddy (`cbc`) installation |
-| Pipeline already running | Show status, ask if user wants to stop and restart |
-| PID file stale (process dead) | `launch-feature-daemon.ps1` auto-cleans, retry start |
-| Launch failed (process died immediately) | Show last 20 lines of log: `Get-Content -Tail 20 .prizmkit/state/daemon/feature-daemon.log` |
-| Feature stuck/blocked | Use `reset-feature.ps1 <F-XXX> --clean --run` for a fresh retry |
-| All features blocked/failed | Show status, suggest daemon-safe recovery: `.\.prizmkit\dev-pipeline\reset-feature.ps1 <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 |
-| PowerShell execution policy blocks script | Run `Set-ExecutionPolicy -Scope Process Bypass` for the current terminal |
-| Pipeline stop failed | Use `Stop-Process -Id <PID> -Force`; inspect AI CLI processes with `Get-Process | Select-String codex` |
-| `.env.local` missing or incomplete | Warn: database connection variables not found. Suggest creating env file with required connection variables for the project's database |
-| Database unreachable | Warn: database features will produce mock-only tests. Suggest checking database service status and connection credentials |
-| Migrations not applied | Warn: tables or schema referenced in migration files not found in database. Suggest applying pending migrations |
+Read `${SKILL_DIR}/references/configuration.md` for the full error handling table (16 entries covering feature-list not found, dependency checks, pipeline state, browser tooling, permission, and deploy failures).
 
 ### Integration Notes
 

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

@@ -0,0 +1,77 @@
+# Configuration Reference — Feature Pipeline Launcher (Windows)
+
+Environment variable mappings for the feature launcher.
+
+## Advanced Config Questions (second AskUserQuestion round)
+
+Asked only when the user chose "Yes" to Advanced config in step 6.
+
+**Question 1 — Session timeout** (multiSelect: false):
+- None (default) — No timeout
+- 30 min — `SESSION_TIMEOUT=1800`
+- 1 hour — `SESSION_TIMEOUT=3600`
+- 2 hours — `SESSION_TIMEOUT=7200`
+
+**Question 2 — Stop on failure** (multiSelect: false):
+- Off (default) — Pipeline continues to next task after failure
+- On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
+
+**Question 3 — Reasoning effort** (multiSelect: false):
+- Default (none) — Use CLI default
+- low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
+- medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
+- high — Thorough reasoning for complex tasks (`PRIZMKIT_EFFORT=high`)
+- xhigh — Extensive reasoning (`PRIZMKIT_EFFORT=xhigh`)
+- max — Maximum reasoning, Claude Code only (`PRIZMKIT_EFFORT=max`)
+
+## Environment Variable Mapping
+
+Translating user responses to env vars:
+
+| Config choice | Environment variable |
+|-----------|---------------------|
+| Critic: On | `ENABLE_CRITIC=true` |
+| Verbose: Off | `VERBOSE=0` |
+| Verbose: On | `VERBOSE=1` |
+| Max retries: N | `MAX_RETRIES=N` |
+| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
+| Stop on failure: On | `STOP_ON_FAILURE=1` |
+| Deploy: Yes | `ENABLE_DEPLOY=1` |
+| Effort: value | `PRIZMKIT_EFFORT=<value>` |
+
+## Advanced Environment Variables
+
+Not exposed in interactive menu, pass via `--env`:
+
+| Variable | Default | Purpose |
+|----------|---------|---------|
+| `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
+| `AUTO_PUSH` | `0` | Auto-push to remote after successful feature (`1` to enable) |
+| `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `dev/{feature_id}-YYYYMMDDHHmm`) |
+| `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
+| `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
+| `PIPELINE_MODE` | (none) | Override mode for all features: `lite`\|`standard`\|`full` |
+| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
+| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
+| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| `.prizmkit/plans/feature-list.json` not found | Tell user to run `feature-planner` skill first |
+| JSON parsing failed | Use the bundled Python validation/status scripts instead of external JSON tools |
+| AI CLI not in PATH | Check Codex (`codex`), Claude (`claude`), or CodeBuddy (`cbc`) installation |
+| Pipeline already running | Show status, ask if user wants to stop and restart |
+| PID file stale (process dead) | `launch-feature-daemon.ps1` auto-cleans, retry start |
+| Launch failed (process died immediately) | Show last 20 lines of log: `Get-Content -Tail 20 .prizmkit/state/daemon/feature-daemon.log` |
+| Feature stuck/blocked | Use `reset-feature.ps1 <F-XXX> --clean --run` for a fresh retry |
+| All features blocked/failed | Show status, suggest daemon-safe recovery: `.\.prizmkit\dev-pipeline\reset-feature.ps1 <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 |
+| PowerShell execution policy blocks script | Run `Set-ExecutionPolicy -Scope Process Bypass` for the current terminal |
+| Pipeline stop failed | Use `Stop-Process -Id <PID> -Force`; inspect AI CLI processes with `Get-Process \| Select-String codex` |
+| 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 |
+| Database unreachable | Warn: database features will produce mock-only tests. Suggest checking database service status and connection credentials |
+| Migrations not applied | Warn: tables or schema referenced in migration files not found in database. Suggest applying pending migrations |

package/bundled/skills-windows/feature-planner/SKILL.md

@@ -60,13 +60,7 @@ When the user provides detailed specifications, rules, or implementation require
 
 ## When to Use
 
-Trigger this skill for requests like:
-- "Add features to existing system", "Continue planning"
-- "Prepare .prizmkit/plans/feature-list.json", "Prepare dev-pipeline input"
-- "Reprioritize features", "Split features"
-- "Plan features for my project" (when the project already exists)
-
-Do NOT use this skill when:
+Trigger conditions are covered by the frontmatter `description`. Do NOT use this skill when:
 - The user wants to plan a new app from scratch → use `app-planner`
 - The user only wants to run the pipeline → use `feature-pipeline-launcher`
 - The user is debugging/refactoring or wants to write source code directly
@@ -115,7 +109,7 @@ Do NOT use this skill when:
    If the script is not available, perform these manual validation checks:
    1. **ID sequence**: All feature IDs are sequential (F-001, F-002, F-003, ...)
    2. **No circular dependencies**: No feature depends (directly or transitively) on itself
-   3. **Description length**: Minimum 15 words per description (error), recommended minimum 30/50/80/100+ for low/medium/high/critical (warning). No upper limit — more detail is always better
+   3. **Description length**: Minimum 15 words per description (error); see §Output Rules for the recommended-length warning thresholds
    4. **Dependency references**: All referenced features in dependencies exist in features array
    5. **Priority enums**: All priority values are exactly "critical", "high", "medium", or "low" (case-sensitive)
    6. **Status enum**: All status values are one of: pending, in_progress, completed, failed, skipped, split, auto_skipped
@@ -362,7 +356,7 @@ Present a consolidated testing summary table at Phase 8, then ask for confirmati
 
 ## Next-Step Execution Policy (after planning)
 
-Recommend invoking `feature-pipeline-launcher` to configure and launch the dev-pipeline. Do NOT recommend running shell scripts directly — that is the launcher's responsibility.
+Recommend invoking `feature-pipeline-launcher` to configure and launch the dev-pipeline. Do NOT recommend running shell scripts directly — that is the launcher's responsibility. Follow the post-planning handoff in §Scope Boundary (never auto-execute).
 
 ## Error Recovery & Resume
 
@@ -399,3 +393,5 @@ After successful validation, report:
 2. Total features + newly added features
 3. Dependency and priority highlights
 4. Recommended next action: `feature-pipeline-launcher`
+
+Then apply the post-planning handoff in §Scope Boundary (ask before proceeding; never auto-execute).