prizmkit 1.1.16 → 1.1.17

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.16",
-  "bundledAt": "2026-04-09T17:14:25.405Z",
-  "bundledFrom": "e2d888c"
+  "frameworkVersion": "1.1.17",
+  "bundledAt": "2026-04-10T11:02:04.397Z",
+  "bundledFrom": "07af4ce"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.16",
+  "version": "1.1.17",
   "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

@@ -164,6 +164,11 @@ This applies to:
 - Use `multiSelect: true` when the user can pick more than one
 - Mark the recommended option first and append "(Recommended)" to its label
 - Use the `description` field to explain trade-offs or implications
+- **Every non-essential question MUST include a "Skip" option** (e.g., "Skip — decide later"). Users should never be forced to answer something they want to defer. Skipped items are simply not written to conventions — they can be added in a future session.
+
+**What can be skipped vs. what cannot:**
+- **Cannot skip**: Intent confirmation (must know the session goal)
+- **Everything else can be skipped**: conventions, tech stack choices, architecture decisions, design direction, etc. If the user skips, move on — do not re-ask or block progress.
 
 **When gathering open-ended information** (e.g., "describe your app idea"), use regular text questions — but follow up with `AskUserQuestion`-based clarifications wherever possible.
 

package/package.json

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