prizmkit 1.0.110 → 1.0.111

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.110",
-  "bundledAt": "2026-03-26T02:24:41.453Z",
-  "bundledFrom": "9b18d27"
+  "frameworkVersion": "1.0.111",
+  "bundledAt": "2026-03-26T05:28:57.400Z",
+  "bundledFrom": "dacaffd"
 }

package/bundled/skills/_metadata.json

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

@@ -130,6 +130,55 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 
 **Resume Detection**: See §Resume Support for checkpoint-based resumption.
 
+## Architecture Decision Capture
+
+During planning, key **framework-level** architectural decisions may emerge. When they do, capture them in the project instruction file so all future AI sessions have this context.
+
+### What Qualifies (ALL must apply)
+
+Only capture decisions that are **framework-shaping** — NOT individual feature details. Qualifying categories:
+
+| Category | Examples |
+|----------|----------|
+| Tech stack choices | PostgreSQL over MongoDB, React over Vue, Node.js runtime |
+| Communication patterns | REST vs GraphQL, WebSocket vs SSE vs polling |
+| Architectural patterns | Monorepo, microservices, monolith, event-driven |
+| Data model strategies | Relational vs document, event sourcing, CQRS |
+| Security architecture | JWT vs session, OAuth provider, RBAC model |
+
+**Do NOT capture**: individual feature implementation details, UI component choices, specific API endpoint designs, or anything scoped to a single feature.
+
+**This is conditional** — most planning sessions will NOT produce architecture decisions. Only capture when genuinely impactful decisions are made during the discussion.
+
+### When to Capture
+
+After Phase 5 (DAG verification), before Phase 6 (JSON generation). At this point decisions are settled.
+
+### How to Capture
+
+1. **Detect platform** — determine which project instruction file to update:
+   - `.claude/` directory exists → append to `CLAUDE.md`
+   - `.codebuddy/` directory exists → append to `CODEBUDDY.md`
+   - Both exist → append to both
+   - Neither exists → skip (no project instruction file)
+
+2. **Check for existing section** — read the target file and look for `### Architecture Decisions` heading:
+   - If heading exists → append new entries below it (avoid duplicates with existing entries)
+   - If heading does not exist → create it at the end of the file
+
+3. **Format** — one line per decision, no feature IDs:
+   ```markdown
+   ### Architecture Decisions
+   - WebSocket for real-time: sub-second latency required for collaboration features
+   - PostgreSQL: relational data model with complex queries, ACID compliance needed
+   - Monorepo structure: shared types between frontend and backend
+   ```
+
+4. **User confirmation** — before writing, show the collected decisions and ask:
+   > "These architecture decisions were identified during planning. Record them to [CLAUDE.md / CODEBUDDY.md]? (Y/n)"
+
+   If user declines, skip without further prompting.
+
 ## Fast Path — Incremental Shortcuts
 
 For simple incremental planning, skip detailed Phase 2-3 analysis to accelerate delivery:

package/package.json

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