prizmkit 1.0.131 → 1.0.132

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.131",
-  "bundledAt": "2026-03-28T07:24:10.796Z",
-  "bundledFrom": "b143c05"
+  "frameworkVersion": "1.0.132",
+  "bundledAt": "2026-03-28T09:29:01.869Z",
+  "bundledFrom": "e0ce79b"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.131",
+  "version": "1.0.132",
   "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/app-planner/SKILL.md

@@ -11,6 +11,20 @@ Plan deliverable features for dev-pipeline in two modes:
 
 Always produce a validated `feature-list.json` that conforms to `dev-pipeline-feature-list`.
 
+## Invocation Commitment (Hard Rule)
+
+**When the user invokes `/app-planner`, you MUST execute the app-planner workflow.** You must NEVER:
+- Decide on the user's behalf that the task "doesn't need app-planner"
+- Skip app-planner to jump directly to spec/plan/implement or any other skill
+- Bypass the interactive phases because you judge the task to be "simple" or "obvious"
+
+If you believe the task is better suited for a different workflow (e.g., fast path via `/prizmkit-plan`), you MUST:
+1. **Explain why** you think a different path is more appropriate
+2. **Ask the user explicitly** whether they want to switch or continue with app-planner
+3. **Only switch if the user confirms** — otherwise proceed with app-planner as invoked
+
+The user chose this skill intentionally. Respect that choice.
+
 ## Scope Boundary (Hard Rule)
 
 **This skill is PLANNING ONLY.** You must NEVER:
@@ -222,11 +236,12 @@ For simple incremental planning, skip detailed Phase 2-3 analysis to accelerate
 
 ### Fast Path Workflow
 1. Read existing `feature-list.json` and confirm scope
-2. Generate next sequential feature IDs
-3. Draft features (title + description + acceptance_criteria + dependencies)
-4. Run validation script immediately
-5. If valid → summarize and recommend next step
-6. If invalid → apply fixes, re-validate (max 2 attempts, then escalate to full workflow)
+2. **User confirmation (mandatory)** — Tell the user: "This qualifies for fast-path (simple incremental addition). Skip detailed Phase 2-3 analysis and draft directly? Or use full workflow?" Only proceed with fast path if user confirms.
+3. Generate next sequential feature IDs
+4. Draft features (title + description + acceptance_criteria + dependencies)
+5. Run validation script immediately
+6. If valid → summarize and recommend next step
+7. If invalid → apply fixes, re-validate (max 2 attempts, then escalate to full workflow)
 
 ### When NOT to Use Fast Path
 - New app planning (always use full workflow)
@@ -238,10 +253,12 @@ For simple incremental planning, skip detailed Phase 2-3 analysis to accelerate
 ### Example Fast Path Session
 ```
 User: "Add email verification to existing user module."
-AI: [Detects incremental mode] 
+AI: [Detects incremental mode]
 AI: [Checks existing plan: found 8 features, user module exists]
 AI: [Qualifies for fast path: 1 feature, low complexity, ≤2 deps]
-AI: "Fast path available. Drafting F-009..."
+AI: "This qualifies for fast-path. Skip detailed analysis and draft directly? Or use full workflow?"
+User: "Fast path is fine."
+AI: "Drafting F-009..."
 AI: [Validates immediately]
 AI: "Ready to proceed to dev-pipeline."
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.131",
+  "version": "1.0.132",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {