prizmkit 1.1.41 → 1.1.46

package/bundled/skills/feature-workflow/SKILL.md

@@ -124,7 +124,7 @@ Ask the user to describe what they want to build. Listen for:
 Ask:
 1. **Existing code** — "Is there existing code I should look at? Which files or directories are relevant?"
 2. **Design documents** — "Do you have any design docs, wireframes, API specs, or PRDs I should read?"
-3. **Knowledge docs** — "Are there related `.prizm-docs/`, README files, or internal wiki pages?"
+3. **Knowledge docs** — "Are there related `.prizmkit/prizm-docs/`, README files, or internal wiki pages?"
 4. **Reference projects** — "Any reference implementations or similar projects I should look at for inspiration?"
 
 Record everything the user provides — these become inputs for Step 1.3.
@@ -139,7 +139,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 |-------|-------------|---------|
 | Agent A | User-provided code paths — read existing source files | Understand current architecture, patterns, conventions |
 | Agent B | User-provided documents — design docs, specs, PRDs | Understand intended requirements and constraints |
-| Agent C | `.prizm-docs/` — root.prizm, L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
+| Agent C | `.prizmkit/prizm-docs/` — root.prizm, L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
 | Agent D | Database/schema files + `.prizmkit/config.json` | Understand data model and tech stack preferences |
 
 **Also gather** (can be included in any agent's task):
@@ -156,7 +156,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 Present what you learned from the parallel reading:
 - Current project structure and patterns (with specific references)
 - Existing data model and schema conventions
-- Known TRAPS and pitfalls from `.prizm-docs/`
+- Known TRAPS and pitfalls from `.prizmkit/prizm-docs/`
 - Integration points with existing modules
 
 Then ask targeted questions based on what you read. **Adapt question depth to the feature complexity** — a simple CRUD feature needs fewer questions than a real-time collaboration system.
@@ -251,7 +251,7 @@ Once brainstorming is complete, produce a structured requirements summary:
 - [Requirement]
 
 ### Reference Materials Reviewed
-- [List of code paths, documents, .prizm-docs/ files that were read]
+- [List of code paths, documents, .prizmkit/prizm-docs/ files that were read]
 
 ### Confirmed by user: ✓
 ```
@@ -292,7 +292,7 @@ AskUserQuestion:
   2. Invoke `/prizmkit-implement` to execute the plan
   3. After implementation, run `/prizmkit-code-review` for quality check
   4. Commit via `/prizmkit-committer` with `feat(<scope>):` prefix
-  5. Run `/prizmkit-retrospective` to sync `.prizm-docs/`
+  5. Run `/prizmkit-retrospective` to sync `.prizmkit/prizm-docs/`
   6. **End workflow** — skip Phase 2/3/4
 - **Add to feature list** → Continue to Phase 2 (Plan via pipeline)
 
@@ -392,7 +392,7 @@ AskUserQuestion:
 
 1. **Initial status check**:
    ```bash
-   dev-pipeline/launch-feature-daemon.sh status
+   .prizmkit/dev-pipeline/launch-feature-daemon.sh status
    ```
 
 2. **Offer monitoring options**:
@@ -402,7 +402,7 @@ AskUserQuestion:
 
 3. **Periodic progress reports** (when user asks):
    ```bash
-   python3 dev-pipeline/scripts/update-feature-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
      --feature-list .prizmkit/plans/feature-list.json \
      --state-dir .prizmkit/state/features \
      --action status
@@ -508,4 +508,4 @@ All internal asset paths use `${SKILL_DIR}` placeholder for cross-IDE compatibil
 - Pipeline execution (Phase 3)
 - Progress updates (Phase 4)
 - Multiple git commits with `feat(<scope>):` prefix
-- Updated `.prizm-docs/` (via prizmkit-retrospective per feature)
+- Updated `.prizmkit/prizm-docs/` (via prizmkit-retrospective per feature)

package/bundled/skills/prizm-kit/SKILL.md

@@ -17,15 +17,15 @@ read docs → plan → implement → code-review → retrospective → committer
 Each task begins by reading context at two levels:
 
 **Application level** (read every session):
-- `.prizm-docs/root.prizm` — L0 project architecture index (modules, tech stack, conventions)
+- `.prizmkit/prizm-docs/root.prizm` — L0 project architecture index (modules, tech stack, conventions)
 - `.prizmkit/plans/project-brief.md` — user's product vision checklist (generated by app-planner)
 - `.prizmkit/config.json` — tech stack config, deploy strategy
 
 **Task level** (read for the specific task):
 - `spec.md` / `plan.md` — task specification and implementation plan
-- `.prizm-docs/<module>.prizm` (L1/L2) — architecture docs for affected modules (TRAPS, DECISIONS, INTERFACES)
+- `.prizmkit/prizm-docs/<module>.prizm` (L1/L2) — architecture docs for affected modules (TRAPS, DECISIONS, INTERFACES)
 
-Each cycle produces spec, plan, and task artifacts that create a traceable record of what was built and why. `.prizm-docs/` stays in sync through retrospective, so the next session starts with up-to-date context.
+Each cycle produces spec, plan, and task artifacts that create a traceable record of what was built and why. `.prizmkit/prizm-docs/` stays in sync through retrospective, so the next session starts with up-to-date context.
 
 **Fast path** — for small, well-scoped changes, always ask user whether to use fast path:
 ```
@@ -42,13 +42,13 @@ PrizmKit supports any development scenario through the same skill chain. `/prizm
 | **Bug Fix** | `spec.md` → `plan.md` → code | Complex defects, regressions, crash fixes. Simple bugs can use fast path directly. |
 | **Refactor** | `spec.md` → `plan.md` → code | Restructure, extract, rename, performance. No behavior change. |
 
-All three follow the same per-task flow. Detailed documentation policies (when to update `.prizm-docs/`, when to skip steps) are defined within each skill — not here.
+All three follow the same per-task flow. Detailed documentation policies (when to update `.prizmkit/prizm-docs/`, when to skip steps) are defined within each skill — not here.
 
 ### Best Practices for AI-Driven Development
 
 **Monorepo structure recommended**: Keep frontend, backend, and shared libraries in one repository. AI needs visibility into the full call chain — cross-repo references are invisible to it. If you have a multi-repo setup, add all related repos to the AI workspace so module boundaries and API contracts are discoverable.
 
-**Module organization**: Ensure every meaningful module has a `.prizm-docs/` L1 doc. AI reads TRAPS and DECISIONS before modifying files — undocumented modules get no guardrails.
+**Module organization**: Ensure every meaningful module has a `.prizmkit/prizm-docs/` L1 doc. AI reads TRAPS and DECISIONS before modifying files — undocumented modules get no guardrails.
 
 **Small, focused tasks**: Break large features into tasks that can each be completed in one AI session. The pipeline handles this automatically via `/prizmkit-plan` task decomposition.
 
@@ -59,23 +59,23 @@ All three follow the same per-task flow. Detailed documentation policies (when t
 | `/prizmkit-plan` | Specify + plan: natural language → spec.md → plan.md + tasks | "specify", "plan", "new feature", "I want to add...", "architect", "break it down" |
 | `/prizmkit-implement` | Execute plan.md tasks, write code (TDD) | "implement", "build", "code it", "start coding" |
 | `/prizmkit-code-review` | Diagnose issues + produce Fix Instructions | "review", "check code", "is it ready to commit" |
-| `/prizmkit-retrospective` | Sync .prizm-docs/ with code changes | "retrospective", "retro", "sync docs", "wrap up" |
+| `/prizmkit-retrospective` | Sync .prizmkit/prizm-docs/ with code changes | "retrospective", "retro", "sync docs", "wrap up" |
 | `/prizmkit-committer` | Safe git commit with Conventional Commits | "commit", "submit", "finish", "ship it" |
 | `/prizmkit-deploy` | Generate/update deployment documentation | "deploy docs", "deployment guide", "how to deploy" |
-| `/prizmkit-init` | Project bootstrap + .prizm-docs/ setup | "init", "initialize", "take over this project" |
+| `/prizmkit-init` | Project bootstrap + .prizmkit/prizm-docs/ setup | "init", "initialize", "take over this project" |
 | `/prizmkit-prizm-docs` | Doc management (init/status/rebuild/validate) | "check docs", "rebuild docs", "validate docs" |
 
 **Reading guide**:
-- Need code structure/modules/interfaces/traps/decisions? → `.prizm-docs/`
+- Need code structure/modules/interfaces/traps/decisions? → `.prizmkit/prizm-docs/`
 
 ## Quick Start (First-Time Setup)
 
 1. `npx prizmkit install .` → installs skills, rules (`prizm-documentation.md`, `prizm-commit-workflow.md`), hooks, platform scaffolding
-2. `/prizmkit-init` → scans project code, generates `.prizm-docs/`, detects tech stack, populates `.prizmkit/config.json`
+2. `/prizmkit-init` → scans project code, generates `.prizmkit/prizm-docs/`, detects tech stack, populates `.prizmkit/config.json`
 3. `/prizmkit-plan` → specify your first feature → produces spec.md + plan.md
 4. `/prizmkit-implement` → TDD implementation following the plan
 5. `/prizmkit-code-review` → review before commit
-6. `/prizmkit-retrospective` → sync `.prizm-docs/` with changes
+6. `/prizmkit-retrospective` → sync `.prizmkit/prizm-docs/` with changes
 7. `/prizmkit-committer` → safe Conventional Commit
 
 > **Note**: Rules and hooks are installed by `npx prizmkit install`, not by `/prizmkit-init`.

package/bundled/skills/prizmkit-committer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-committer"
-description: "Pure git commit workflow with safety checks. Stages files, generates Conventional Commits message, and commits. Does NOT modify .prizm-docs/ — run /prizmkit-retrospective first. Trigger on: 'commit', 'submit', 'finish', 'done', 'ship it'. (project)"
+description: "Pure git commit workflow with safety checks. Stages files, generates Conventional Commits message, and commits. Does NOT modify .prizmkit/prizm-docs/ — run /prizmkit-retrospective first. Trigger on: 'commit', 'submit', 'finish', 'done', 'ship it'. (project)"
 ---
 
 # PrizmKit Committer
@@ -15,7 +15,7 @@ description: "Pure git commit workflow with safety checks. Stages files, generat
 | Required State | Check | If Missing |
 |---|---|---|
 | Uncommitted changes exist | `git status` shows modified/added/untracked files | Inform user "nothing to commit" and stop |
-| `.prizm-docs/` synced (feature/refactor) | `/prizmkit-retrospective` has run | Run `/prizmkit-retrospective` first |
+| `.prizmkit/prizm-docs/` synced (feature/refactor) | `/prizmkit-retrospective` has run | Run `/prizmkit-retrospective` first |
 | Code review passed (pipeline mode) | `review-report.md` in artifact directory has `## Verdict: PASS` | Run `/prizmkit-code-review` first |
 
 ### Workflow
@@ -66,6 +66,8 @@ Ask user: "Push to remote?"
 - Yes: `git push`
 - No: Stop
 
+**Headless mode**: If the skill was invoked with `--headless` in the args (e.g., `/prizmkit-committer --headless feat(F-001): ...`), **SKIP this step entirely**. Do NOT ask the question. Do NOT push. Stop after Step 5 verification. Headless mode is used by autonomous pipeline sessions where there is no human to answer interactive prompts.
+
 ## Example
 
 **Feature commit:**

package/bundled/skills/prizmkit-implement/SKILL.md

@@ -30,9 +30,9 @@ description: "Execute plan.md tasks with TDD approach. Respects task ordering an
 Before implementation, load context once:
 
 1. **Task context**: Read `plan.md` (including Tasks section) and `spec.md` from the artifact directory. If other companion documents exist in the directory (e.g., `refactor-analysis.md`), read them for additional context.
-2. **Architecture context**: Read `.prizm-docs/root.prizm` (L0 — project overview, module index, tech stack, conventions) and relevant L1/L2 docs for affected modules. Pay special attention to TRAPS (known pitfalls) and DECISIONS (architectural choices).
+2. **Architecture context**: Read `.prizmkit/prizm-docs/root.prizm` (L0 — project overview, module index, tech stack, conventions) and relevant L1/L2 docs for affected modules. Pay special attention to TRAPS (known pitfalls) and DECISIONS (architectural choices).
 
-> `.prizm-docs/` uses a 3-level hierarchy: L0 (`root.prizm`) is the project-wide index. L1 (e.g., `auth.prizm`) covers a module — its key files, interfaces, dependencies, traps, and decisions. L2 is for sub-modules with their own complexity. Implement reads these docs to avoid repeating known mistakes; `/prizmkit-retrospective` is responsible for updating them after implementation.
+> `.prizmkit/prizm-docs/` uses a 3-level hierarchy: L0 (`root.prizm`) is the project-wide index. L1 (e.g., `auth.prizm`) covers a module — its key files, interfaces, dependencies, traps, and decisions. L2 is for sub-modules with their own complexity. Implement reads these docs to avoid repeating known mistakes; `/prizmkit-retrospective` is responsible for updating them after implementation.
 
 ## Execution
 

package/bundled/skills/prizmkit-init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-init"
-description: "Project takeover and bootstrap. Scans any project, generates Prizm docs and project brief. Use this skill whenever a user opens a new project for the first time, says 'initialize', 'set up PrizmKit', 'take over this project', 'bootstrap', 'scan this codebase', 'init', or when .prizm-docs/ doesn't exist yet. Also use when PrizmKit was just installed via npx but not yet initialized. (project)"
+description: "Project takeover and bootstrap. Scans any project, generates Prizm docs and project brief. Use this skill whenever a user opens a new project for the first time, says 'initialize', 'set up PrizmKit', 'take over this project', 'bootstrap', 'scan this codebase', 'init', or when .prizmkit/prizm-docs/ doesn't exist yet. Also use when PrizmKit was just installed via npx but not yet initialized. (project)"
 ---
 
 # PrizmKit Init
@@ -11,7 +11,7 @@ Project takeover and bootstrap skill. Scans any project (brownfield or greenfiel
 - Taking over a new project (brownfield or greenfield)
 - User says "initialize PrizmKit", "set up PrizmKit", "take over this project"
 - First time using PrizmKit on a project
-- After `npx prizmkit install` when project has no `.prizm-docs/`
+- After `npx prizmkit install` when project has no `.prizmkit/prizm-docs/`
 
 ### When NOT to Use
 - All artifacts exist and are up to date → use `/prizmkit-prizm-docs` (Update) instead if you only want to resync docs
@@ -38,14 +38,14 @@ Scan all init artifacts and display their status:
 
 | Artifact | Path | Check |
 |----------|------|-------|
-| Prizm docs | `.prizm-docs/` | Directory exists + `root.prizm` present |
+| Prizm docs | `.prizmkit/prizm-docs/` | Directory exists + `root.prizm` present |
 | Runtime config | `.prizmkit/config.json` | File exists |
 | Project brief | `.prizmkit/plans/project-brief.md` | File exists |
 
 Display status table to user:
 ```
 Init Status Check:
-  [exists]  .prizm-docs/          (N files)
+  [exists]  .prizmkit/prizm-docs/          (N files)
   [exists]  .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 ```
@@ -59,7 +59,7 @@ Init Status Check:
 Each subsequent phase checks its artifact's action before executing:
 - `action == skip` → output "Skipped (exists)" and move on
 - `action == generate | regenerate` → run normally
-- **Special case for `.prizm-docs/`**:
+- **Special case for `.prizmkit/prizm-docs/`**:
   - `skip` = **Update** mode: preserve existing L1/L2 docs, re-scan tech stack, merge changes, check for missing docs (see `${SKILL_DIR}/references/update-supplement.md`)
   - `regenerate` = **Reinitialize**: overwrite everything
 
@@ -70,8 +70,8 @@ BROWNFIELD WORKFLOW (existing project):
 2. Map directory structure using a TWO-TIER model — flat structures lose the nesting relationships that AI needs to navigate the codebase:
    - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `src/`, `internal/`, `lib/`)
    - SUB-MODULES: directories INSIDE a top-level module (e.g. `src/routes/`, `src/models/`)
-   - A sub-module maps to `.prizm-docs/<M>/<S>.prizm`, never to `.prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
-   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`, `dev-pipeline/`
+   - A sub-module maps to `.prizmkit/prizm-docs/<M>/<S>.prizm`, never to `.prizmkit/prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizmkit/prizm-docs/`, `dev-pipeline/`
    - **Scan command** — run this to get a 2-level directory tree (excludes noise directories):
      ```bash
      find . -maxdepth 2 -type d \
@@ -79,7 +79,7 @@ BROWNFIELD WORKFLOW (existing project):
        -not -path '*/dist/*' -not -path '*/build/*' \
        -not -path '*/__pycache__/*' -not -path '*/vendor/*' \
        -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
-       -not -path '*/.prizmkit/*' -not -path '*/.prizm-docs/*' \
+       -not -path '*/.prizmkit/*' -not -path '*/.prizmkit/prizm-docs/*' \
        -not -path '*/dev-pipeline/*' -not -path '*/target/*' \
        | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
      ```
@@ -151,10 +151,10 @@ Detect database and deployment signals, then ask 1-2 brief questions. This phase
 
 **Phase 5: Prizm Documentation Generation**
 Invoke prizmkit-prizm-docs (Init operation), passing the two-tier module structure from Phase 4:
-  - Create `.prizm-docs/` directory structure mirroring the source tree (sub-module dirs become subdirectories under `.prizm-docs/<top-level>/`)
+  - Create `.prizmkit/prizm-docs/` directory structure mirroring the source tree (sub-module dirs become subdirectories under `.prizmkit/prizm-docs/<top-level>/`)
   - Generate `root.prizm` (L0) with project meta and MODULE_INDEX listing only top-level modules. If module count > 15, use MODULE_GROUPS format instead (group by functional domain).
   - For each module entry in MODULE_INDEX/MODULE_GROUPS, include keyword tags extracted from the module's source files — scan for: exported symbols, imported packages, domain terms in file/directory names. Format: `- module-name [tag1, tag2, tag3]: ...`. Tags help AI match user intent to relevant modules.
-  - Generate L1 docs for top-level modules at `.prizm-docs/<M>.prizm` and for sub-modules at `.prizm-docs/<M>/<S>.prizm`
+  - Generate L1 docs for top-level modules at `.prizmkit/prizm-docs/<M>.prizm` and for sub-modules at `.prizmkit/prizm-docs/<M>/<S>.prizm`
   - Create `changelog.prizm`
   - Skip L2 (lazy generation) — L2 is generated on first file modification, saving tokens upfront
 
@@ -231,7 +231,7 @@ GREENFIELD WORKFLOW (new project):
   - Record answers in `config.json` `tech_stack` with `"_auto_detected": false` (user-provided, not auto-detected)
   - If user is unsure, skip tech_stack — it can be populated later on re-init after code exists
 - Phase 4.5: Run Infrastructure Quick Scan — in greenfield mode, no auto-detection is possible, so only ask the 2 brief questions (database need and deployment target). If user is unsure, skip — these can be configured later via `app-planner` or `/prizmkit-deploy`.
-- Phase 5: Create minimal `.prizm-docs/` with just `root.prizm` skeleton (populate TECH_STACK from user answers if provided)
+- Phase 5: Create minimal `.prizmkit/prizm-docs/` with just `root.prizm` skeleton (populate TECH_STACK from user answers if provided)
 - Phase 7: Generate project brief (greenfield flow — ask user about project goals, see Phase 7 above)
 - Phases 6, 8: Same as brownfield (Phase 8 Report recommends `/prizmkit-plan` for first feature)
 
@@ -243,7 +243,7 @@ $ /prizmkit-init
 
 Platform detected: Claude Code
 Init Status Check:
-  [missing] .prizm-docs/
+  [missing] .prizmkit/prizm-docs/
   [missing] .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 → All missing, generating everything.
@@ -266,10 +266,10 @@ Infrastructure Quick Scan:
   → Written to CLAUDE.md ### Infrastructure
 
 Modules discovered:
-  src/routes/     → .prizm-docs/routes.prizm (12 files)
-  src/models/     → .prizm-docs/models.prizm (8 files)
-  src/services/   → .prizm-docs/services.prizm (15 files)
-  src/middleware/  → .prizm-docs/middleware.prizm (5 files)
+  src/routes/     → .prizmkit/prizm-docs/routes.prizm (12 files)
+  src/models/     → .prizmkit/prizm-docs/models.prizm (8 files)
+  src/services/   → .prizmkit/prizm-docs/services.prizm (15 files)
+  src/middleware/  → .prizmkit/prizm-docs/middleware.prizm (5 files)
 
 Project brief: inferred from codebase → confirmed by user
   → .prizmkit/plans/project-brief.md
@@ -288,7 +288,7 @@ UPDATE SUPPLEMENT (runs after tech stack merge in Update mode):
 $ /prizmkit-init
 
 Init Status Check:
-  [exists]  .prizm-docs/          (12 files)
+  [exists]  .prizmkit/prizm-docs/          (12 files)
   [exists]  .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 

package/bundled/skills/prizmkit-plan/SKILL.md

@@ -36,7 +36,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
    - If `artifact_dir` is provided → use it directly
    - If not provided → scan `.prizmkit/specs/` for existing `###-*` directories, find highest numeric prefix, next = highest + 1 (zero-padded to 3 digits; start at `001` if empty). Create `.prizmkit/specs/###-task-slug/`
    - Auto-generate 2-10 word task slug from description
-3. Load project context: read `.prizm-docs/root.prizm` and relevant L1/L2 docs
+3. Load project context: read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs
 4. Generate `spec.md` from template (`${SKILL_DIR}/assets/spec-template.md`):
    - Fill sections based on the task description — all sections are optional, include only what is relevant
    - `[NEEDS CLARIFICATION]` markers for all ambiguous items
@@ -56,7 +56,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
 **Steps:**
 
 1. Read `spec.md` from the artifact directory
-2. Load project context if not already loaded in Phase 0: read `.prizm-docs/root.prizm` and relevant L1/L2 docs
+2. Load project context if not already loaded in Phase 0: read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs
 3. Resolve any remaining `[NEEDS CLARIFICATION]` by proposing solutions
 4. Generate `plan.md` from template (`${SKILL_DIR}/assets/plan-template.md`):
    - Change approach (how the changes integrate with existing system)
@@ -67,7 +67,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
    - Risk assessment
    - Behavior preservation strategy (if the task modifies existing behavior — include what must remain unchanged and how to verify)
 5. Cross-check: every goal in spec.md maps to plan components — unmapped goals = coverage gaps
-6. Check alignment with `.prizm-docs/root.prizm` RULES section
+6. Check alignment with `.prizmkit/prizm-docs/root.prizm` RULES section
 
 ### Phase 2: Task Generation (plan.md → Tasks section)
 

package/bundled/skills/prizmkit-plan/references/verification-checklist.md

@@ -40,8 +40,8 @@ Run this checklist after generating the Tasks section in plan.md. Fix any issues
 
 ## Rules Alignment
 
-- [ ] No spec or plan element conflicts with `.prizm-docs/root.prizm` RULES MUST/NEVER directives
-- [ ] Tech stack choices in plan.md match `.prizm-docs/root.prizm` TECH_STACK (if defined)
+- [ ] No spec or plan element conflicts with `.prizmkit/prizm-docs/root.prizm` RULES MUST/NEVER directives
+- [ ] Tech stack choices in plan.md match `.prizmkit/prizm-docs/root.prizm` TECH_STACK (if defined)
 
 ## Database Design (skip if no Data Model section)
 

package/bundled/skills/prizmkit-prizm-docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-prizm-docs"
-description: "Project documentation specification and standard for AI-optimized progressive context loading. Defines the .prizm-docs/ 3-level hierarchy (L0/L1/L2), format rules, size limits, and loading protocol. Use this skill to: bootstrap docs for new projects (init), check doc freshness (status), regenerate stale modules (rebuild), validate format compliance (validate), or migrate existing docs (migrate). For incremental doc updates after code changes, use /prizmkit-retrospective instead — it is the sole writer of .prizm-docs/ during development. Trigger on: 'initialize docs', 'check doc status', 'rebuild docs', 'validate docs', 'migrate docs', 'docs are stale', 'prizm docs'. (project)"
+description: "Project documentation specification and standard for AI-optimized progressive context loading. Defines the .prizmkit/prizm-docs/ 3-level hierarchy (L0/L1/L2), format rules, size limits, and loading protocol. Use this skill to: bootstrap docs for new projects (init), check doc freshness (status), regenerate stale modules (rebuild), validate format compliance (validate), or migrate existing docs (migrate). For incremental doc updates after code changes, use /prizmkit-retrospective instead — it is the sole writer of .prizmkit/prizm-docs/ during development. Trigger on: 'initialize docs', 'check doc status', 'rebuild docs', 'validate docs', 'migrate docs', 'docs are stale', 'prizm docs'. (project)"
 ---
 
 # Prizm Docs - AI Documentation Framework
@@ -30,53 +30,53 @@ This skill handles 6 operations. When invoked, determine the user's intent and e
 |--------|----------------------|--------------------------|
 | **Role** | Documentation SPECIFICATION + BOOTSTRAP | Incremental WRITER during development |
 | **When** | Project setup, health checks, migrations | After feature completion, before commit |
-| **Writes** | Initial .prizm-docs/ structure (init, rebuild, migrate) | Incremental updates to existing .prizm-docs/ |
+| **Writes** | Initial .prizmkit/prizm-docs/ structure (init, rebuild, migrate) | Incremental updates to existing .prizmkit/prizm-docs/ |
 | **Reads** | Source code structure (for init/rebuild) | git diff + code changes (for sync) |
-| **Knowledge** | Defines format rules, size limits, loading protocol | Extracts TRAPS/RULES/DECISIONS into `.prizm-docs/` |
+| **Knowledge** | Defines format rules, size limits, loading protocol | Extracts TRAPS/RULES/DECISIONS into `.prizmkit/prizm-docs/` |
 
 **Key principle**: `/prizmkit-prizm-docs` defines WHAT the docs should look like and bootstraps them. `/prizmkit-retrospective` is the SOLE WRITER that keeps docs in sync with code during ongoing development.
 
 ## Operation: Init
 
-Bootstrap .prizm-docs/ for the current project.
-PRECONDITION: No .prizm-docs/ directory exists, or user confirms overwrite.
+Bootstrap .prizmkit/prizm-docs/ for the current project.
+PRECONDITION: No .prizmkit/prizm-docs/ directory exists, or user confirms overwrite.
 → Read `${SKILL_DIR}/references/op-init.md` for detailed steps.
 
 ## Operation: Update
 
-Update .prizm-docs/ to reflect recent code changes.
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+Update .prizmkit/prizm-docs/ to reflect recent code changes.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 → Read `${SKILL_DIR}/references/op-update.md` for detailed steps.
 
 ## Operation: Status
 
 Check freshness of all .prizm docs.
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 → Read `${SKILL_DIR}/references/op-status.md` for detailed steps.
 
 ## Operation: Rebuild
 
 Regenerate docs for a specific module from scratch. Requires a module path argument.
-PRECONDITION: .prizm-docs/ exists. Module path is valid.
+PRECONDITION: .prizmkit/prizm-docs/ exists. Module path is valid.
 → Read `${SKILL_DIR}/references/op-rebuild.md` for detailed steps.
 
 ## Operation: Validate
 
 Check format compliance and consistency of all .prizm docs.
-PRECONDITION: .prizm-docs/ exists.
+PRECONDITION: .prizmkit/prizm-docs/ exists.
 → Read `${SKILL_DIR}/references/op-validate.md` for detailed steps.
 
 ## Operation: Migrate
 
-Convert existing documentation to .prizm-docs/ format.
-PRECONDITION: Existing docs/ or docs/AI_CONTEXT/ directory. No .prizm-docs/ (or user confirms overwrite).
+Convert existing documentation to .prizmkit/prizm-docs/ format.
+PRECONDITION: Existing docs/ or docs/AI_CONTEXT/ directory. No .prizmkit/prizm-docs/ (or user confirms overwrite).
 
 STEPS:
 1. DISCOVER existing docs: Scan docs/, docs/AI_CONTEXT/, README.md, ARCHITECTURE.md, and any structured documentation files.
 2. EXTRACT information from existing docs: project metadata, module descriptions, architecture patterns, rules, decisions, dependencies.
 3. MAP existing doc content to Prizm levels: project-wide info -> L0 root.prizm, module-level info -> L1 docs (MODULE, FILES, RESPONSIBILITY, KEY_FILES, DEPENDENCIES), detailed module info -> L2 docs (INTERFACES, DATA_FLOW, TRAPS, DECISIONS, domain-specific sections).
 4. CONVERT prose content to KEY: value format. Strip markdown formatting, tables, diagrams. Condense explanatory text into single-line values.
-5. GENERATE .prizm-docs/ structure following standard init procedure but seeded with extracted information instead of scanning source code alone.
+5. GENERATE .prizmkit/prizm-docs/ structure following standard init procedure but seeded with extracted information instead of scanning source code alone.
 6. VALIDATE migrated docs against Prizm format rules and size limits.
 7. REPORT migration summary: files processed, content mapped, information that could not be automatically converted (requires manual review).
 
@@ -99,7 +99,7 @@ For detailed protocol specifications, see prizm-docs-format.md:
 
 **Init output (Node.js project):**
 ```
-Generated .prizm-docs/:
+Generated .prizmkit/prizm-docs/:
   root.prizm (L0) — 3 modules in MODULE_INDEX
   routes.prizm (L1) — 12 files, 4 interfaces
   models.prizm (L1) — 8 files, 3 interfaces
@@ -110,8 +110,8 @@ Generated .prizm-docs/:
 **Update after adding new API endpoint:**
 ```
 Changed: src/routes/avatar.ts (A), src/models/user.ts (M)
-Updated: .prizm-docs/routes.prizm — added avatar.ts to KEY_FILES, new POST /api/avatar interface
-Updated: .prizm-docs/models.prizm — updated User interface with avatar_url field
-Skipped: .prizm-docs/services.prizm — no changes in services module
+Updated: .prizmkit/prizm-docs/routes.prizm — added avatar.ts to KEY_FILES, new POST /api/avatar interface
+Updated: .prizmkit/prizm-docs/models.prizm — updated User interface with avatar_url field
+Skipped: .prizmkit/prizm-docs/services.prizm — no changes in services module
 Appended: changelog.prizm — "routes | add: avatar upload endpoint"
 ```