prizmkit 1.1.5 → 1.1.7

package/bundled/dev-pipeline/templates/bug-fix-list-schema.json

@@ -1,9 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Dev-Pipeline Bug Fix List",
-  "description": "Schema for bug-fix-list.json — standardized input for the Bug Fix Pipeline",
+  "description": "Schema for bug-fix-list.json \u2014 standardized input for the Bug Fix Pipeline",
   "type": "object",
-  "required": ["$schema", "project_name", "bugs"],
+  "required": [
+    "$schema",
+    "project_name",
+    "bugs"
+  ],
   "properties": {
     "$schema": {
       "type": "string",
@@ -29,9 +33,14 @@
       "items": {
         "type": "object",
         "required": [
-          "id", "title", "description", "severity",
-          "error_source", "verification_type",
-          "acceptance_criteria", "status"
+          "id",
+          "title",
+          "description",
+          "severity",
+          "error_source",
+          "verification_type",
+          "acceptance_criteria",
+          "status"
         ],
         "properties": {
           "id": {
@@ -42,7 +51,7 @@
           "title": {
             "type": "string",
             "minLength": 1,
-            "description": "Bug title — brief description of the symptom"
+            "description": "Bug title \u2014 brief description of the symptom"
           },
           "description": {
             "type": "string",
@@ -51,17 +60,29 @@
           },
           "severity": {
             "type": "string",
-            "enum": ["critical", "high", "medium", "low"],
+            "enum": [
+              "critical",
+              "high",
+              "medium",
+              "low"
+            ],
             "description": "critical=crash/data-loss; high=core-feature-broken; medium=workaround-exists; low=cosmetic"
           },
           "priority": {
             "type": "string",
-            "enum": ["high", "medium", "low"],
-            "description": "Fix priority. Pipeline processes high before medium before low; within same level, array order determines sequence."
+            "enum": [
+              "critical",
+              "high",
+              "medium",
+              "low"
+            ],
+            "description": "Fix priority. Pipeline processes critical before high before medium before low; within same level, array order determines sequence."
           },
           "error_source": {
             "type": "object",
-            "required": ["type"],
+            "required": [
+              "type"
+            ],
             "description": "Structured error source information extracted from various input formats",
             "properties": {
               "type": {
@@ -92,7 +113,9 @@
               },
               "reproduction_steps": {
                 "type": "array",
-                "items": { "type": "string" },
+                "items": {
+                  "type": "string"
+                },
                 "description": "User-reported reproduction steps (when type=user_report)"
               }
             }
@@ -104,28 +127,44 @@
           },
           "affected_modules": {
             "type": "array",
-            "items": { "type": "string" },
+            "items": {
+              "type": "string"
+            },
             "description": "Known affected module names (optional, triage will auto-detect)"
           },
           "environment": {
             "type": "object",
             "description": "Environment where the bug occurs",
             "properties": {
-              "os": { "type": "string" },
-              "runtime": { "type": "string" },
-              "browser": { "type": "string" },
-              "version": { "type": "string" }
+              "os": {
+                "type": "string"
+              },
+              "runtime": {
+                "type": "string"
+              },
+              "browser": {
+                "type": "string"
+              },
+              "version": {
+                "type": "string"
+              }
             }
           },
           "verification_type": {
             "type": "string",
-            "enum": ["automated", "manual", "hybrid"],
+            "enum": [
+              "automated",
+              "manual",
+              "hybrid"
+            ],
             "description": "automated=unit/integration-test; manual=human-UAT; hybrid=both"
           },
           "acceptance_criteria": {
             "type": "array",
             "minItems": 1,
-            "items": { "type": "string" },
+            "items": {
+              "type": "string"
+            },
             "description": "Conditions that must be met for the bug to be considered fixed"
           },
           "status": {
@@ -142,6 +181,23 @@
               "skipped"
             ],
             "description": "Bug fix status, maps to pipeline phases"
+          },
+          "critic": {
+            "type": "boolean",
+            "description": "Enable adversarial critic review for this bug fix. Default: true for high severity bugs, false for others.",
+            "default": false
+          },
+          "critic_count": {
+            "type": "integer",
+            "description": "Number of parallel critic agents. 1 = single critic, 3 = multi-critic voting. Default: 1 for high severity, omit for others.",
+            "enum": [
+              1,
+              3
+            ]
+          },
+          "model": {
+            "type": "string",
+            "description": "AI model ID for this bug fix. Overrides $MODEL env var."
           }
         }
       }
@@ -150,19 +206,43 @@
       "type": "object",
       "description": "Global context for all bug fixes in this batch",
       "properties": {
-        "tech_stack": { "type": "string" },
-        "language": { "type": "string" },
-        "runtime": { "type": "string" },
-        "frontend_framework": { "type": "string" },
-        "frontend_styling": { "type": "string" },
-        "backend_framework": { "type": "string" },
-        "database": { "type": "string" },
-        "orm": { "type": "string" },
-        "testing_strategy": { "type": "string" },
-        "bundler": { "type": "string" },
-        "project_type": { "type": "string" },
-        "ci_pipeline": { "type": "string" }
+        "tech_stack": {
+          "type": "string"
+        },
+        "language": {
+          "type": "string"
+        },
+        "runtime": {
+          "type": "string"
+        },
+        "frontend_framework": {
+          "type": "string"
+        },
+        "frontend_styling": {
+          "type": "string"
+        },
+        "backend_framework": {
+          "type": "string"
+        },
+        "database": {
+          "type": "string"
+        },
+        "orm": {
+          "type": "string"
+        },
+        "testing_strategy": {
+          "type": "string"
+        },
+        "bundler": {
+          "type": "string"
+        },
+        "project_type": {
+          "type": "string"
+        },
+        "ci_pipeline": {
+          "type": "string"
+        }
       }
     }
   }
-}
+}

package/bundled/dev-pipeline/templates/feature-list-schema.json

@@ -3,17 +3,17 @@
   "title": "Dev-Pipeline Feature List",
   "description": "Schema for .dev-pipeline/feature-list.json",
   "type": "object",
-  "required": ["$schema", "app_name", "features"],
+  "required": ["$schema", "project_name", "features"],
   "properties": {
     "$schema": {
       "type": "string",
       "const": "dev-pipeline-feature-list-v1"
     },
-    "app_name": {
+    "project_name": {
       "type": "string",
       "minLength": 1
     },
-    "app_description": {
+    "project_description": {
       "type": "string"
     },
     "created_at": {
@@ -47,8 +47,8 @@
           },
           "priority": {
             "type": "string",
-            "enum": ["high", "medium", "low"],
-            "description": "Feature priority. Pipeline processes high before medium before low; within same level, array order determines sequence."
+            "enum": ["critical", "high", "medium", "low"],
+            "description": "Feature priority. Pipeline processes critical before high before medium before low; within same level, array order determines sequence."
           },
           "estimated_complexity": {
             "type": "string",

package/bundled/dev-pipeline/templates/refactor-list-schema.json

@@ -1,9 +1,13 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Dev-Pipeline Refactor List",
-  "description": "Schema for refactor-list.json — standardized input for the Refactor Pipeline",
+  "description": "Schema for refactor-list.json \u2014 standardized input for the Refactor Pipeline",
   "type": "object",
-  "required": ["$schema", "project_name", "refactors"],
+  "required": [
+    "$schema",
+    "project_name",
+    "refactors"
+  ],
   "properties": {
     "$schema": {
       "type": "string",
@@ -29,9 +33,17 @@
       "items": {
         "type": "object",
         "required": [
-          "id", "title", "description", "scope", "type",
-          "priority", "complexity", "behavior_preservation",
-          "acceptance_criteria", "dependencies", "status"
+          "id",
+          "title",
+          "description",
+          "scope",
+          "type",
+          "priority",
+          "complexity",
+          "behavior_preservation",
+          "acceptance_criteria",
+          "dependencies",
+          "status"
         ],
         "properties": {
           "id": {
@@ -42,7 +54,7 @@
           "title": {
             "type": "string",
             "minLength": 1,
-            "description": "Refactor title — brief description of the change"
+            "description": "Refactor title \u2014 brief description of the change"
           },
           "description": {
             "type": "string",
@@ -55,39 +67,65 @@
             "properties": {
               "files": {
                 "type": "array",
-                "items": { "type": "string" },
+                "items": {
+                  "type": "string"
+                },
                 "description": "File paths affected by this refactor"
               },
               "modules": {
                 "type": "array",
-                "items": { "type": "string" },
+                "items": {
+                  "type": "string"
+                },
                 "description": "Module names affected by this refactor"
               }
             }
           },
           "type": {
             "type": "string",
-            "enum": ["extract", "rename", "restructure", "simplify", "decouple", "migrate"],
+            "enum": [
+              "extract",
+              "rename",
+              "restructure",
+              "simplify",
+              "decouple",
+              "migrate"
+            ],
             "description": "extract=extract-function/module; rename=rename-symbols; restructure=move/reorganize; simplify=reduce-complexity; decouple=remove-dependencies; migrate=tech-migration"
           },
           "priority": {
             "type": "string",
-            "enum": ["critical", "high", "medium", "low"],
+            "enum": [
+              "critical",
+              "high",
+              "medium",
+              "low"
+            ],
             "description": "Refactor priority. Pipeline processes critical before high before medium before low; within same level, array order determines sequence."
           },
           "complexity": {
             "type": "string",
-            "enum": ["low", "medium", "high"],
+            "enum": [
+              "low",
+              "medium",
+              "high"
+            ],
             "description": "Estimated complexity of the refactor"
           },
           "behavior_preservation": {
             "type": "object",
-            "required": ["strategy"],
+            "required": [
+              "strategy"
+            ],
             "description": "Strategy for ensuring no behavior changes",
             "properties": {
               "strategy": {
                 "type": "string",
-                "enum": ["test-gate", "snapshot", "manual"],
+                "enum": [
+                  "test-gate",
+                  "snapshot",
+                  "manual"
+                ],
                 "description": "test-gate=existing-tests-must-pass; snapshot=before/after-snapshot-comparison; manual=human-verification"
               },
               "existing_tests": {
@@ -96,7 +134,9 @@
               },
               "new_tests_needed": {
                 "type": "array",
-                "items": { "type": "string" },
+                "items": {
+                  "type": "string"
+                },
                 "description": "New tests that should be written before refactoring"
               }
             }
@@ -104,7 +144,9 @@
           "acceptance_criteria": {
             "type": "array",
             "minItems": 1,
-            "items": { "type": "string" },
+            "items": {
+              "type": "string"
+            },
             "description": "Conditions that must be met for the refactor to be considered complete"
           },
           "dependencies": {
@@ -133,6 +175,19 @@
           "estimated_lines": {
             "type": "integer",
             "description": "Estimated number of lines affected by this refactor"
+          },
+          "critic": {
+            "type": "boolean",
+            "description": "Enable adversarial critic review for this refactor. Default: true for critical/high priority refactors, false for others.",
+            "default": false
+          },
+          "critic_count": {
+            "type": "integer",
+            "description": "Number of parallel critic agents. 1 = single critic, 3 = multi-critic voting. Default: 3 for critical, 1 for high, omit for others.",
+            "enum": [
+              1,
+              3
+            ]
           }
         }
       }
@@ -141,19 +196,43 @@
       "type": "object",
       "description": "Global context for all refactors in this batch",
       "properties": {
-        "tech_stack": { "type": "string" },
-        "language": { "type": "string" },
-        "runtime": { "type": "string" },
-        "frontend_framework": { "type": "string" },
-        "frontend_styling": { "type": "string" },
-        "backend_framework": { "type": "string" },
-        "database": { "type": "string" },
-        "orm": { "type": "string" },
-        "testing_strategy": { "type": "string" },
-        "bundler": { "type": "string" },
-        "project_type": { "type": "string" },
-        "ci_pipeline": { "type": "string" }
+        "tech_stack": {
+          "type": "string"
+        },
+        "language": {
+          "type": "string"
+        },
+        "runtime": {
+          "type": "string"
+        },
+        "frontend_framework": {
+          "type": "string"
+        },
+        "frontend_styling": {
+          "type": "string"
+        },
+        "backend_framework": {
+          "type": "string"
+        },
+        "database": {
+          "type": "string"
+        },
+        "orm": {
+          "type": "string"
+        },
+        "testing_strategy": {
+          "type": "string"
+        },
+        "bundler": {
+          "type": "string"
+        },
+        "project_type": {
+          "type": "string"
+        },
+        "ci_pipeline": {
+          "type": "string"
+        }
       }
     }
   }
-}
+}

package/bundled/dev-pipeline/tests/test_auto_skip.py

@@ -31,7 +31,7 @@ def _make_feature(fid, title="Feature", deps=None, status="pending"):
 def _make_feature_list(features):
     return {
         "$schema": "dev-pipeline-feature-list-v1",
-        "app_name": "test-app",
+        "project_name": "test-app",
         "features": features,
     }
 

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.5",
+  "version": "1.1.7",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -71,6 +71,13 @@
       "hasAssets": true,
       "hasScripts": false
     },
+    "prizmkit-verify": {
+      "description": "Automated framework verification for PrizmKit's 4-layer architecture. Checks structural integrity, contract consistency, and cross-scenario alignment.",
+      "tier": "1",
+      "category": "prizmkit-skill",
+      "hasAssets": false,
+      "hasScripts": true
+    },
     "feature-workflow": {
       "description": "One-stop entry point for feature development. Orchestrates feature-planner → feature-pipeline-launcher → background execution. Handles multi-feature batch development from a single request.",
       "tier": "companion",
@@ -184,7 +191,8 @@
         "refactor-planner",
         "refactor-pipeline-launcher",
         "bug-fix-workflow",
-        "recovery-workflow"
+        "recovery-workflow",
+        "prizmkit-verify"
       ]
     },
     "minimal": {

package/bundled/skills/app-planner/SKILL.md

@@ -40,8 +40,11 @@ If you believe the task is better suited for a different workflow, you MUST:
 **Your ONLY writable outputs are:**
 1. `project-brief.md` (project root — accumulated project context brief)
 2. `.prizmkit/project-conventions.json` (project convention answers)
-3. Architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
-4. Draft backups in `.prizmkit/planning/`
+3. `.prizm-docs/root.prizm` (if architecture decisions are captured — see Architecture Decision Capture section)
+   - Contains architecture decisions, tech stack rationale, and key constraints
+   - Used as input by feature-planner and other workflows
+4. Architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
+5. Draft backups in `.prizmkit/planning/`
 
 **After planning is complete**, you MUST:
 1. Present the summary of captured vision, constraints, and decisions
@@ -158,6 +161,14 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 
 After Phase 2, if framework-shaping architecture decisions emerged during planning (tech stack, communication patterns, data model strategies — not individual feature details), read `${SKILL_DIR}/references/architecture-decisions.md` and follow the capture flow. Most sessions will NOT produce architecture decisions — only capture when genuinely impactful.
 
+**Handoff to feature-planner**: Captured architecture decisions MUST be written to `.prizm-docs/root.prizm` so that feature-planner can read them as context. This ensures all downstream planners (feature, bug, refactor) share consistent architectural understanding.
+
+**How it works**:
+1. If decisions are captured → create `.prizm-docs/root.prizm` with decision summaries
+2. Also append decisions to `CLAUDE.md` / `CODEBUDDY.md` for human reference
+3. When feature-planner is invoked, it will read `.prizm-docs/root.prizm` as prerequisite context
+4. Feature decomposition will respect captured architecture decisions (no conflicting tech choices)
+
 ## Project Brief Accumulation
 
 During interactive planning, maintain a `project-brief.md` at the project root as a simple checklist of product ideas.
@@ -209,6 +220,6 @@ When the session appears to be ending:
 After all checkpoints pass, present a summary and recommend next steps:
 
 1. **Summary**: List captured vision, tech stack, constraints, architecture decisions, and project brief status
-2. **Primary recommendation**: Invoke `feature-planner` to decompose the application into features and generate `feature-list.json`
+2. **Primary recommendation**: Invoke `feature-planner` to decompose the application into features and generate `feature-list.json` (schema: `dev-pipeline-feature-list-v1`, uses `project_name` field for the app name)
 3. **Alternative**: If the user wants to continue refining the vision or constraints, stay in app-planner
 4. **Artifacts produced**: List files written (`project-brief.md`, `.prizmkit/project-conventions.json`, architecture decisions if any)

package/bundled/skills/bug-fix-workflow/SKILL.md

@@ -83,6 +83,8 @@ For trivial bugs with clear root cause and minimal scope:
 
 **Goal**: Fully understand the bug before touching any code. Vague bug reports lead to incorrect fixes that mask the real issue or introduce new bugs.
 
+**Fast Path Decision Point**: After initial information gathering (Step 1.1), evaluate the Fast Path Eligibility Criteria above. If ALL criteria are met, ask the user: "This looks like a straightforward fix. Use fast path? (Y/n)". If yes, skip directly to the Fast Path Workflow (branch setup already done in Phase 0). If no or uncertain, continue with full diagnosis.
+
 **CRITICAL RULE**: Ask as many questions as needed until the bug is fully understood. Do NOT rush into code. A misdiagnosed bug leads to a wrong fix, which is worse than no fix.
 
 #### Step 1.1: Initial Bug Information Gathering

package/bundled/skills/bug-planner/SKILL.md

@@ -116,6 +116,7 @@ ALERT: Error rate spike: 500 errors/min on /api/login endpoint
 - Environment (ask or auto-detect from logs)
 - Verification type (suggest `automated` by default, ask user)
 - Acceptance criteria (auto-suggest based on description, user can edit)
+- Model override (optional; if specified, overrides $MODEL env var for this bug fix)
 
 **Per-bug clarification** — if the bug's root cause, reproduction steps, expected behavior, or scope is unclear from the provided information, ask focused questions one at a time (cite the unclear point, give a recommended answer with rationale) until the bug is fully understood. Do not finalize a bug entry with ambiguous details. No limit on the number of questions per bug.
 
@@ -152,13 +153,21 @@ Only finalize the bug entry after user confirms all three points.
 
 ### Phase 3: Prioritization & Review
 
-1. **Auto-assign priorities**: Based on severity (critical=1, high=2, medium=3, low=4), adjustable by user
+1. **Auto-assign priorities**: Based on severity (critical → high, high → high, medium → medium, low → low), adjustable by user
+   
+   **Severity → Priority Mapping**:
+   - `critical` severity → `high` priority (treated with highest urgency)
+   - `high` severity → `high` priority
+   - `medium` severity → `medium` priority
+   - `low` severity → `low` priority
+   
+   Note: Severity has 4 levels (critical, high, medium, low) but Priority has 3 levels (high, medium, low). Both critical and high severity bugs map to high priority.
 2. **Display summary table**:
    ```
    ID    | Title                        | Severity | Priority | Verification
-   B-001 | Login null reference crash    | critical | 1        | automated
-   B-002 | CSV export Chinese encoding   | medium   | 3        | hybrid
-   B-003 | Slow dashboard loading        | low      | 4        | manual
+   B-001 | Login null reference crash    | critical | high     | automated
+   B-002 | CSV export Chinese encoding   | medium   | medium   | hybrid
+   B-003 | Slow dashboard loading        | low      | low      | manual
    ```
 3. **Ask for adjustments**: "Want to reorder priorities, change severity, or remove any bugs?"
 4. **Detect potential duplicates**: If two bugs have similar error messages or affected modules, warn user
@@ -309,6 +318,52 @@ Affected Features: F-003 (1 bug), F-012 (1 bug), none (1 bug)
 
 ---
 
+## Adversarial Critic Review (Testing Defaults)
+
+All bug fixes support optional critic review for additional quality assurance. The critic mechanism is disabled by default but can be enabled per-bug based on severity and complexity.
+
+### Default Critic Behavior
+
+| Severity | `critic` | `critic_count` | Rationale |
+|----------|----------|----------------|-----------|
+| critical | `true` | `1` | Single critic review for critical bugs |
+| high | `true` | `1` | Single critic review for high-severity bugs |
+| medium | `false` | (omitted) | Skip critic for medium-severity bugs |
+| low | `false` | (omitted) | Skip critic for low-severity bugs |
+
+- `critic: true` — Enable adversarial review after fix implementation
+- `critic_count: 1` — Single critic agent reviews the fix
+- Critic verifies: fix addresses root cause, no regressions introduced, acceptance criteria met
+
+**User Override**: During Phase 2 or Phase 3, users can opt to enable/disable critic on a per-bug basis.
+
+---
+
+## Browser Verification
+
+**Browser verification is a feature-pipeline capability only.** Bug fixes use the `verification_type` field instead:
+
+- `verification_type: automated` — Use unit/integration tests to verify the fix
+- `verification_type: manual` — Describe manual testing steps in acceptance criteria (including any browser verification steps)
+- `verification_type: hybrid` — Combine automated tests with manual browser verification steps
+
+For UI-related bugs that require visual verification (e.g., "Button doesn't show error message"), describe the verification steps in your acceptance criteria:
+
+Example:
+```
+Bug Title: Login error message not displaying
+Verification Type: manual
+Acceptance Criteria:
+  1. Navigate to /login with invalid credentials
+  2. Verify error message "Invalid email or password" appears below the email field
+  3. Verify error message is red (#FF0000)
+  4. Verify form fields are still enabled and can be re-submitted
+```
+
+The bugfix pipeline AI will use these criteria during manual verification.
+
+---
+
 ## Integration with Bug Fix Pipeline
 
 After `bug-fix-list.json` is generated, the user can: