prizmkit 1.1.15 → 1.1.17

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.15",
-  "bundledAt": "2026-04-09T16:41:49.608Z",
-  "bundledFrom": "aed6378"
+  "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.15",
+  "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

@@ -12,7 +12,7 @@ Plan an application from idea to actionable project context through interactive
 - Architecture decision capture
 - Project brief accumulation (`.prizmkit/plans/project-brief.md`)
 
-This skill captures **what to build and why**. For **feature decomposition and `.prizmkit/plans/feature-list.json` generation**, hand off to `feature-planner`.
+This skill captures **project-level context only**: vision, tech stack, conventions, architecture decisions, and project brief. It does NOT do feature decomposition or generate `feature-list.json` — that is `feature-planner`'s job.
 
 For adding features to an **existing** project that already has a project brief, use `feature-planner` directly.
 
@@ -38,10 +38,10 @@ If you believe the task is better suited for a different workflow, you MUST:
 2. Project conventions and architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
 
 **After planning is complete**, you MUST:
-1. Present the summary of captured vision, constraints, and decisions
-2. **Ask the user explicitly** whether they want to proceed to feature decomposition
-3. If the user wants to continue exploring → stay in app-planner
-4. **NEVER auto-execute** the pipeline, feature-planner, or any implementation step
+1. Present the summary of captured project-level context (vision, conventions, architecture decisions, project brief)
+2. List the artifacts produced and suggest possible next steps (e.g., `feature-planner`, `prizmkit-plan`, etc.) — but do NOT auto-invoke any of them
+3. **NEVER auto-execute** the pipeline, feature-planner, or any implementation step
+4. **NEVER generate `feature-list.json`** — that is exclusively `feature-planner`'s responsibility
 
 ## When to Use
 
@@ -154,7 +154,6 @@ This applies to:
 - Project conventions
 - Tech stack selection
 - Architecture decisions
-- Handoff recommendations
 - Session exit gates
 - Brownfield prerequisite check
 - Any other decision point
@@ -165,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.
 
@@ -184,7 +188,7 @@ Route by answer:
   - Load `${SKILL_DIR}/references/brainstorm-guide.md` and follow its structured ideation process (Phases A-D)
   - Brainstorm Phase D output serves as the Vision Summary (CP-AP-2)
   - After brainstorm completes, use `AskUserQuestion`: "Ideas are taking shape. What's next?"
-    - **Proceed to feature decomposition (Recommended)** — hand off to feature-planner
+    - **Continue to project planning (Recommended)** — capture tech stack, conventions, and architecture decisions
     - **Continue refining** — keep brainstorming
     - **Save draft & exit** — save progress to .prizmkit/planning/
   - **Checkpoints in explore mode**: CP-AP-0 (required), CP-AP-1 (required), CP-AP-2 (from brainstorm output), CP-AP-3 (only if user proceeds to Phase 2), CP-AP-4 and CP-AP-5 (only if user transitions to produce mode)
@@ -300,7 +304,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
        - Question: "No UI/UX design docs found. Would you like to establish design direction?"
        - Options: "Establish design direction now (Recommended)", "Skip for now", "I have external designs"
 3. Capture architecture decisions and finalize project brief
-4. Hand off to `feature-planner` for feature decomposition
+4. Present completion summary with artifacts produced and possible next steps
 
 ### Checkpoints (Mandatory Gates)
 
@@ -313,7 +317,7 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 | **CP-AP-2** | Vision Summary | Goal/users/differentiators confirmed by user. For brownfield: existing purpose confirmed or refined. | 1-2 |
 | **CP-AP-3** | Frontend Design Evaluated | For frontend projects: checked for existing UI/UX design system; user was asked if missing. **Auto-pass** for backend-only or non-UI projects. | 2 |
 | **CP-AP-4** | Project Brief Accumulated | `.prizmkit/plans/project-brief.md` exists at `.prizmkit/plans/` with at least 3 ideas listed. For brownfield: already-implemented items marked `[x]` count toward this total. | 3 |
-| **CP-AP-5** | Handoff Ready | All app-level context captured; user confirmed readiness for feature decomposition | 4 |
+| **CP-AP-5** | Planning Complete | All project-level context captured: conventions, tech stack, architecture decisions, project brief finalized | 4 |
 
 ## Architecture Decision Capture
 
@@ -321,7 +325,7 @@ After Phase 2, if framework-shaping architecture decisions emerged during planni
 
 **How it works**:
 1. If decisions are captured → append to `CLAUDE.md` / `CODEBUDDY.md` under `### Architecture Decisions` section
-2. Feature-planner and other downstream skills read `CLAUDE.md` / `CODEBUDDY.md` as standard context, so they automatically receive these decisions
+2. Downstream skills (feature-planner, prizmkit-plan, etc.) read `CLAUDE.md` / `CODEBUDDY.md` as standard context, so they automatically receive these decisions
 3. Do NOT write directly to `.prizm-docs/root.prizm` — that file is maintained by `prizmkit-prizm-docs` and `prizmkit-retrospective`. If the project needs `.prizm-docs/`, recommend the user run `prizmkit-prizm-docs` init after planning.
 
 ## Project Brief Accumulation
@@ -349,13 +353,20 @@ When the session appears to be ending:
    - **Save draft & exit** — write current progress as draft to `.prizmkit/planning/`
    - **Abandon** — exit without saving
 
-## Handoff to feature-planner
+## Completion Summary
+
+After all checkpoints pass, present a summary and end the session:
+
+1. **Summary** (as text): List all project-level artifacts produced:
+   - Project conventions → `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions`
+   - Tech stack → `.prizmkit/config.json`
+   - Architecture decisions (if any) → `CLAUDE.md` / `CODEBUDDY.md` `### Architecture Decisions`
+   - Project brief → `.prizmkit/plans/project-brief.md`
 
-After all checkpoints pass, present a summary and use `AskUserQuestion` for next steps:
+2. **Suggest possible next steps** (as text, NOT auto-invoked):
+   > Project-level planning is complete. When you're ready, here are some possible next steps:
+   > - `feature-planner` — decompose the project into features and generate `feature-list.json`
+   > - `prizmkit-plan` — start working on a specific feature directly
+   > - `prizmkit-prizm-docs` — initialize or update project documentation
 
-1. **Summary** (as text): List captured vision, tech stack, constraints, architecture decisions, and project brief status
-2. Use `AskUserQuestion`: "Planning complete! What's next?"
-   - **Proceed to feature decomposition (Recommended)** — invoke `feature-planner` to break down features into `.prizmkit/plans/feature-list.json`
-   - **Continue refining** — stay in app-planner to adjust vision or constraints
-   - **Done for now** — exit with artifacts saved
-3. **Artifacts produced**: List files written (`.prizmkit/plans/project-brief.md`, project conventions and architecture decisions in `CLAUDE.md` / `CODEBUDDY.md`)
+   **Do NOT invoke any of these.** The user decides what to do next, in their own time.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.15",
+  "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": {