prizmkit 1.0.118 → 1.0.119

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.118",
-  "bundledAt": "2026-03-26T15:57:17.490Z",
-  "bundledFrom": "f6b1f2d"
+  "frameworkVersion": "1.0.119",
+  "bundledAt": "2026-03-27T15:01:36.094Z",
+  "bundledFrom": "3b42eb5"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.118",
+  "version": "1.0.119",
   "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/prizmkit-retrospective/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-retrospective"
-description: "Incremental .prizm-docs/ maintainer. Performs two jobs: (1) structural sync — update .prizm-docs/ KEY_FILES/INTERFACES/DEPENDENCIES, (2) architecture knowledge — inject TRAPS/RULES/DECISIONS into .prizm-docs/. All project knowledge lives in .prizm-docs/ . Run after code review passes and before committing. Trigger on: 'retrospective', 'retro', 'update docs', 'sync docs', 'wrap up', 'done with feature', 'feature complete'. (project)"
+description: "Incremental .prizm-docs/ maintainer + deploy guide generator. Performs three jobs: (1) structural sync — update .prizm-docs/ KEY_FILES/INTERFACES/DEPENDENCIES, (2) architecture knowledge — inject TRAPS/RULES/DECISIONS into .prizm-docs/, (3) deploy guide — detect new frameworks/tools and record setup instructions to deploy_guide.md. All project knowledge lives in .prizm-docs/ . Run after code review passes and before committing. Trigger on: 'retrospective', 'retro', 'update docs', 'sync docs', 'wrap up', 'done with feature', 'feature complete'. (project)"
 ---
 
 # PrizmKit Retrospective
@@ -11,10 +11,11 @@ All project knowledge is maintained in a single store:
 |-------|----------|---------|---------|
 | **Architecture Index** | `.prizm-docs/` | MODULE, FILES, INTERFACES, DEPENDENCIES, TRAPS, RULES, DECISIONS | AI quickly locates code structure, interfaces, known pitfalls, and key design decisions |
 
-**This skill performs two jobs in one pass:**
+**This skill performs three jobs in one pass:**
 
 1. **Structural Sync** — reflect what changed in code → `.prizm-docs/` (KEY_FILES, INTERFACES, DEPENDENCIES, file counts)
 2. **Architecture Knowledge** — inject TRAPS, RULES, and DECISIONS → `.prizm-docs/`. All knowledge is consolidated in `.prizm-docs/`.
+3. **Deploy Guide** — detect new frameworks/tools and record setup instructions → `deploy_guide.md`
 
 No other skill writes to `.prizm-docs/`. This is the sole writer during ongoing development. For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` instead.
 
@@ -150,6 +151,132 @@ When writing TRAPS:
 
 ---
 
+## Job 3: Deploy Guide Maintenance (`deploy_guide.md`)
+
+When new frameworks or tools that require **manual setup steps** are introduced, record them in `deploy_guide.md` at the project root. This ensures installation, configuration, and deployment knowledge is systematically documented for the team.
+
+### When to Run Job 3
+
+Run this job **only when new frameworks/tools are detected** in the current changeset. Skip entirely if no new framework was introduced.
+
+### Step 3-1: Detect New Frameworks
+
+From the `git diff --cached` (or `git diff`) output already collected in Job 1, check for newly added entries in dependency manifest files:
+
+```bash
+# Check for newly added dependencies in common manifest files
+git diff --cached -U0 -- package.json requirements*.txt Pipfile pyproject.toml go.mod Cargo.toml pom.xml build.gradle Gemfile composer.json docker-compose*.yml Dockerfile .tool-versions 2>/dev/null | grep '^\+' | grep -v '^\+\+\+' | head -30
+```
+
+**Trigger conditions** (ANY match → proceed to Step 3-2):
+- New dependency added to `package.json` (dependencies/devDependencies)
+- New package in `requirements.txt`, `pyproject.toml`, `Pipfile`, `go.mod`, `Cargo.toml`, `pom.xml`, `build.gradle`, `Gemfile`, `composer.json`
+- New service in `docker-compose*.yml` (e.g., database, cache, message queue)
+- New `Dockerfile` created or base image changed
+- New system tool in `.tool-versions`, `.nvmrc`, `.python-version`
+- New CI/CD configuration file added (`.github/workflows/*.yml`, `.gitlab-ci.yml`, `Jenkinsfile`)
+
+**Filter out** (do NOT record):
+- Patch version bumps of existing dependencies (e.g., `1.2.3` → `1.2.4`)
+- Dev-only tools that need no manual setup (linters, formatters, type checkers)
+- Transitive dependencies (lock file changes without manifest changes)
+
+### Step 3-2: Record Framework Info
+
+For each detected new framework/tool, gather the following information from the code changes and dependency files:
+
+| Field | Description | Source |
+|-------|-------------|--------|
+| **Name** | Framework/tool name | Package name from manifest |
+| **Version** | Installed version or constraint | Version spec from manifest |
+| **Purpose** | Why it was introduced | Infer from code usage, feature context, or commit message |
+| **Install Command** | How to install locally | Standard install command for the ecosystem |
+| **Key Config** | Config files or env vars needed | Scan for new config files, `.env` entries, or env references in code |
+| **Notes** | Setup gotchas, required services, manual steps | Infer from Dockerfile, docker-compose, README references, or TRAPS |
+
+### Step 3-3: Update `deploy_guide.md`
+
+Write or append to `deploy_guide.md` at the project root using this template:
+
+```markdown
+# Deploy Guide
+
+> Auto-maintained by PrizmKit retrospective. Manual edits are preserved.
+> Last updated: YYYY-MM-DD
+
+## Frameworks & Tools
+
+### <Framework Name>
+
+- **Version**: <version constraint>
+- **Purpose**: <why this framework is used>
+- **Install**:
+  ```bash
+  <install command>
+  ```
+- **Key Config**:
+  - `<config file or env var>`: <description>
+- **Notes**:
+  - <any setup gotchas, required external services, manual steps>
+```
+
+**Update rules**:
+- If `deploy_guide.md` does not exist → create it with the header and first framework entry
+- If `deploy_guide.md` exists → check if the framework already has a section (match by `### <Name>` heading). If yes, update version and any changed config. If no, append a new section.
+- Preserve any manually added content (sections not matching the template are left untouched)
+- Keep entries sorted alphabetically by framework name within `## Frameworks & Tools`
+
+**Stage the file**:
+```bash
+git add deploy_guide.md
+```
+
+### Example
+
+After adding PostgreSQL via docker-compose and Prisma ORM to a Node.js project:
+
+```markdown
+# Deploy Guide
+
+> Auto-maintained by PrizmKit retrospective. Manual edits are preserved.
+> Last updated: 2026-03-27
+
+## Frameworks & Tools
+
+### PostgreSQL
+
+- **Version**: 16
+- **Purpose**: Primary relational database for user data, orders, and product catalog
+- **Install**:
+  ```bash
+  docker compose up -d postgres
+  ```
+- **Key Config**:
+  - `DATABASE_URL` (env): PostgreSQL connection string, format `postgresql://user:pass@host:5432/dbname`
+  - `docker-compose.yml`: Service `postgres` with volume `pgdata`
+- **Notes**:
+  - Requires Docker running locally
+  - Run `npx prisma migrate deploy` after first start to initialize schema
+
+### Prisma
+
+- **Version**: ^5.20.0
+- **Purpose**: ORM for type-safe database access and schema migrations
+- **Install**:
+  ```bash
+  npm install prisma @prisma/client
+  npx prisma generate
+  ```
+- **Key Config**:
+  - `prisma/schema.prisma`: Database schema definition
+  - `DATABASE_URL` (env): Shared with PostgreSQL connection
+- **Notes**:
+  - After schema changes: `npx prisma migrate dev --name <description>`
+  - Generate client after pull: `npx prisma generate`
+```
+
+---
+
 ## Final: Changelog + Stage
 
 **3a.** Append to `.prizm-docs/changelog.prizm`:
@@ -160,6 +287,8 @@ When writing TRAPS:
 **3b.** Stage all doc changes:
 ```bash
 git add .prizm-docs/
+# Stage deploy guide if it was created/updated
+git add deploy_guide.md 2>/dev/null || true
 ```
 
 **3c.** Handoff:
@@ -189,4 +318,5 @@ The pipeline enforces a **docs pass condition**: `.prizm-docs/` must show change
 
 - `.prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
 - `.prizm-docs/changelog.prizm` — Appended entries
-- All `.prizm-docs/` changes staged via `git add .prizm-docs/`
+- `deploy_guide.md` — New framework/tool setup instructions (only when new frameworks detected)
+- All `.prizm-docs/` changes and `deploy_guide.md` staged via `git add`

package/package.json

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