prizmkit 1.1.42 → 1.1.46

package/bundled/skills/prizmkit-prizm-docs/references/op-init.md

@@ -1,8 +1,8 @@
 # Operation: Init — Detailed Steps
 
-Bootstrap .prizm-docs/ for the current project.
+Bootstrap .prizmkit/prizm-docs/ for the current project.
 
-PRECONDITION: No .prizm-docs/ directory exists, or user confirms overwrite.
+PRECONDITION: No .prizmkit/prizm-docs/ directory exists, or user confirms overwrite.
 
 STEPS:
 1. Detect project type by scanning for build system files (go.mod, package.json, requirements.txt, Cargo.toml, pom.xml, *.csproj). Identify primary language, framework, build command, test command, and entry points.
@@ -10,16 +10,16 @@ STEPS:
    - A directory qualifies as a module if it contains source files forming a logical unit, contains entry/config/interface files, contains qualifying sub-modules, or is referenced by multiple modules as a dependency.
    - TOP-LEVEL modules: directories directly under project root (or under src/ for src-based layouts) that qualify.
    - SUB-MODULES: directories INSIDE a top-level module that qualify. Listed in the parent L1 doc's SUBDIRS section.
-   - HIERARCHY RULE: directory X inside top-level module M maps to .prizm-docs/<M>/<X>.prizm, never to .prizm-docs/<X>.prizm.
-   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/. If total module count > 30, ask user for include/exclude patterns.
-3. Create .prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizm-docs/<M>/.
+   - HIERARCHY RULE: directory X inside top-level module M maps to .prizmkit/prizm-docs/<M>/<X>.prizm, never to .prizmkit/prizm-docs/<X>.prizm.
+   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizmkit/prizm-docs/, dev-pipeline/. If total module count > 30, ask user for include/exclude patterns.
+3. Create .prizmkit/prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizmkit/prizm-docs/<M>/.
 4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX with multi-level entries as needed for efficient navigation (constrained by 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, PATTERNS, and CROSS_CUTTING (cross-module concerns spanning 2+ modules). Set PRIZM_VERSION: 4. Max 4KB. No UPDATED timestamp — git tracks modification times.
    - If `.prizmkit/plans/project-brief.md` exists: add `PROJECT_BRIEF: .prizmkit/plans/project-brief.md` to root.prizm (generated by prizmkit-init). If not present, skip — prizmkit-init Phase 7 will add it later.
    - If module count > 15: use MODULE_GROUPS format instead of MODULE_INDEX — group modules by functional domain (3-8 domains, inferred from directory structure and module responsibilities). See prizm-docs-format.md for MODULE_GROUPS format.
    - For each module entry, auto-generate 3-6 keyword tags by scanning the module's key source files for: exported function/class names, imported library names, domain-specific terms in file/directory names. Add tags in square brackets after the module name (e.g., `- auth [login, session, jwt]: ...`). Tags are optional but recommended for projects with 10+ modules.
 5. Generate L1 .prizm files (structural index only) for ALL modules, each at its correct mirrored path:
-   - Top-level module M → write .prizm-docs/<M>.prizm (include SUBDIRS section with pointers to sub-module docs)
-   - Sub-module S inside M → write .prizm-docs/<M>/<S>.prizm
+   - Top-level module M → write .prizmkit/prizm-docs/<M>.prizm (include SUBDIRS section with pointers to sub-module docs)
+   - Sub-module S inside M → write .prizmkit/prizm-docs/<M>/<S>.prizm
    Each L1 includes MODULE (full relative path), FILES count, RESPONSIBILITY, SUBDIRS with pointers, KEY_FILES (5-10 most important), DEPENDENCIES (imports, imported-by, external), RULES (1-3 most critical only). L1 does NOT include INTERFACES, DATA_FLOW, TRAPS, or DECISIONS (those are L2, generated lazily). Max 4KB each.
 6. Skip L2 docs during init — L2 is created lazily on first file modification or when AI needs deep understanding (ON_DEEP_READ trigger). L2 contains behavioral detail: INTERFACES, DATA_FLOW, TRAPS, DECISIONS, full RULES, domain-specific sections.
 7. Create changelog.prizm with initial entry: `- root | add: initialized prizm documentation framework`
@@ -35,12 +35,12 @@ After initialization, L2 docs are created incrementally:
 
 ON_MODIFY trigger:
 - First time AI modifies a file in sub-module S within module M:
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc, then proceeds with modification
 - This ensures L2 docs have real depth, written when AI has actual context
 
 ON_DEEP_READ trigger:
 - When AI needs to deeply understand a module but not modify it (e.g., code review, architecture analysis, dependency tracing, explaining complex logic):
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc for future reference
 - This ensures L2 docs are available for read-heavy analysis tasks, not just modifications

package/bundled/skills/prizmkit-prizm-docs/references/op-rebuild.md

@@ -2,7 +2,7 @@
 
 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.
 
 STEPS:
 1. Delete existing L1 and all L2 docs for the specified module.

package/bundled/skills/prizmkit-prizm-docs/references/op-status.md

@@ -2,10 +2,10 @@
 
 Check freshness of all .prizm docs.
 
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 
 STEPS:
-1. Get last git modification time of root.prizm via `git log -1 --format="%ai" -- .prizm-docs/root.prizm`.
+1. Get last git modification time of root.prizm via `git log -1 --format="%ai" -- .prizmkit/prizm-docs/root.prizm`.
 2. Count commits since that time via `git log --since="<timestamp>" --oneline | wc -l`.
 3. For each L1/L2 doc, compare git modification time of the .prizm file (`git log -1 --format="%ai" -- <prizm-file>`) against latest git modification of source files in that module (`git log -1 --format="%ai" -- <module-path>/`).
 4. Classify each doc as: FRESH (prizm file updated after latest source change), STALE (source changed more recently than prizm file), MISSING (module exists but no .prizm doc).

package/bundled/skills/prizmkit-prizm-docs/references/op-update.md

@@ -1,8 +1,8 @@
 # Operation: Update — Detailed Steps
 
-Update .prizm-docs/ to reflect recent code changes.
+Update .prizmkit/prizm-docs/ to reflect recent code changes.
 
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 
 STEPS:
 1. Get changed files via `git diff --cached --name-status`. If nothing staged, use `git diff --name-status`. If no git changes at all, do full rescan comparing code against existing docs — this includes checking for modules that have source files but no L2 doc.
@@ -14,6 +14,6 @@ STEPS:
 6a. **L2 gap check** (runs during full rescan mode only — when no git changes detected): For each existing module in MODULE_INDEX, check if L2 doc exists. If L2 is missing and the module has source files with meaningful logic (not trivial config/wrapper) → create L2 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS, CHANGELOG. This ensures Update fills documentation gaps left by previous sessions.
 7. Append entries to changelog.prizm using format: `- <module-path> | <verb>: <description>`
 8. Enforce size limits: L0 > 4KB -> consolidate. L1 > 4KB -> trim KEY_FILES descriptions, ensure RULES <= 3 entries. L2 > 5KB -> split or archive.
-9. Stage updated .prizm files via `git add .prizm-docs/`
+9. Stage updated .prizm files via `git add .prizmkit/prizm-docs/`
 
 OUTPUT: List of updated/created/skipped docs with reasons.

package/bundled/skills/prizmkit-prizm-docs/references/op-validate.md

@@ -2,7 +2,7 @@
 
 Check format compliance and consistency of all .prizm docs.
 
-PRECONDITION: .prizm-docs/ exists.
+PRECONDITION: .prizmkit/prizm-docs/ exists.
 
 STEPS:
 1. FORMAT CHECK: Verify all .prizm files use KEY: value format. Flag any prose paragraphs, code blocks (```), markdown headers (##), emoji, ASCII art, or horizontal rules. Flag TRAPS entries missing severity prefix ([CRITICAL], [HIGH], or [LOW]). Note: [REVIEW] preceding severity (e.g., `[REVIEW][HIGH]`) is a valid temporary staleness marker, not a format violation.

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

@@ -1,18 +1,18 @@
 ---
 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 .prizmkit/prizm-docs/ maintainer. Performs two jobs: (1) structural sync — update .prizmkit/prizm-docs/ KEY_FILES/INTERFACES/DEPENDENCIES, (2) architecture knowledge — inject TRAPS/RULES/DECISIONS into .prizmkit/prizm-docs/. All project knowledge lives in .prizmkit/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
 
 | Store | Location | Content | Purpose |
 |-------|----------|---------|---------|
-| **Architecture Index** | `.prizm-docs/` | MODULE, FILES, INTERFACES, DEPENDENCIES, TRAPS, RULES, DECISIONS | AI quickly locates code structure, interfaces, known pitfalls, and key design decisions |
+| **Architecture Index** | `.prizmkit/prizm-docs/` | MODULE, FILES, INTERFACES, DEPENDENCIES, TRAPS, RULES, DECISIONS | AI quickly locates code structure, interfaces, known pitfalls, and key design decisions |
 
 **This skill handles both structural sync and knowledge injection 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/`
+1. **Structural Sync** — reflect what changed in code → `.prizmkit/prizm-docs/` (KEY_FILES, INTERFACES, DEPENDENCIES, file counts)
+2. **Architecture Knowledge** — inject TRAPS, RULES, and DECISIONS → `.prizmkit/prizm-docs/`
 
 For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` instead.
 
@@ -38,7 +38,7 @@ For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` inst
 ---
 
 ### Job 1: Structural Sync (always runs)
-Synchronize `.prizm-docs/` structure with actual codebase changes from this session.
+Synchronize `.prizmkit/prizm-docs/` structure with actual codebase changes from this session.
 → Read `${SKILL_DIR}/references/structural-sync-steps.md` for the detailed procedure.
 
 **Key outputs**: Updated L1 file counts, L2 INTERFACES/DATA_FLOW, changelog entries, stale TRAPS cleanup.
@@ -72,20 +72,20 @@ Inject newly discovered project knowledge (TRAPS, RULES, DECISIONS) into archite
 
 ## Final: Changelog + Stage
 
-**3a.** Append to `.prizm-docs/changelog.prizm`:
+**3a.** Append to `.prizmkit/prizm-docs/changelog.prizm`:
 - Format: `<module-path> | <verb>: <one-line description>`
 - Verbs: add, update, fix, remove, refactor, rename, deprecate
 - One entry per meaningful change, not one per file
 
 **3b.** Stage all doc changes:
 ```bash
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **HANDOFF:** `/prizmkit-committer`
 
 ## Output
 
-- `.prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
-- `.prizm-docs/changelog.prizm` — Appended entries
-- All `.prizm-docs/` changes staged via `git add`
+- `.prizmkit/prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
+- `.prizmkit/prizm-docs/changelog.prizm` — Appended entries
+- All `.prizmkit/prizm-docs/` changes staged via `git add`

package/bundled/skills/prizmkit-retrospective/references/knowledge-injection-steps.md

@@ -6,7 +6,7 @@
 - `review-report.md` in the artifact directory — read the findings and fix instructions. If this file exists, use it as a source for pre-categorized decisions and findings.
 - `plan.md` in the artifact directory — read planned vs actual
 - Any companion documents in the artifact directory (e.g., `refactor-analysis.md`, `fix-report.md`) — read what was discovered
-- The relevant `.prizm-docs/` L1/L2 docs for affected modules
+- The relevant `.prizmkit/prizm-docs/` L1/L2 docs for affected modules
 
 **2b.** Extract knowledge from what was **observed in code**, not invented:
 
@@ -38,9 +38,9 @@ When writing TRAPS:
 - Only record decisions that a future AI session would benefit from knowing
 - Do NOT record obvious implementation details that can be derived by reading the code
 
-**QUALITY GATE**: Every item must answer: "If a new AI session reads only `.prizm-docs/` and this entry, does it gain actionable understanding?" If not, discard. Do not record trivially observable code patterns — the AI can read the code directly.
+**QUALITY GATE**: Every item must answer: "If a new AI session reads only `.prizmkit/prizm-docs/` and this entry, does it gain actionable understanding?" If not, discard. Do not record trivially observable code patterns — the AI can read the code directly.
 
-**2c.** Inject into the correct `.prizm-docs/` file:
+**2c.** Inject into the correct `.prizmkit/prizm-docs/` file:
 - Module-level TRAPS/RULES/DECISIONS → the affected **L2** `.prizm` file. If the target L2 does not exist, create it first using the L2 GENERATION TEMPLATE before injecting knowledge. (TRAPS/DECISIONS/RULES belong in L2, not L1.)
 - Project-level RULES/PATTERNS → `root.prizm` (respect the current format — MODULE_INDEX or MODULE_GROUPS — do not convert between them during injection)
 - Cross-module concerns spanning 2+ modules → `root.prizm` CROSS_CUTTING section

package/bundled/skills/prizmkit-retrospective/references/structural-sync-steps.md

@@ -5,7 +5,7 @@
 git diff HEAD --name-status
 ```
 
-**1b.** Read `.prizm-docs/root.prizm` to get MODULE_INDEX (or MODULE_GROUPS). Map each changed file to its module.
+**1b.** Read `.prizmkit/prizm-docs/root.prizm` to get MODULE_INDEX (or MODULE_GROUPS). Map each changed file to its module.
 
 **1c.** Classify changes:
 - `A` (added) → add to KEY_FILES, check for new INTERFACES

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

@@ -27,11 +27,11 @@ User says:
 Pipeline commands (for reference — Phase 1.3 will present these as a selectable option):
 
 ```bash
-./dev-pipeline/run-recovery.sh                    # Auto-detect and recover
-./dev-pipeline/run-recovery.sh detect              # Detection report only
-./dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
-./dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
-./dev-pipeline/run-recovery.sh run --model <model> # Override AI model
+./.prizmkit/dev-pipeline/run-recovery.sh                    # Auto-detect and recover
+./.prizmkit/dev-pipeline/run-recovery.sh detect              # Detection report only
+./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
+./.prizmkit/dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
+./.prizmkit/dev-pipeline/run-recovery.sh run --model <model> # Override AI model
 ```
 
 ### When to use pipeline vs interactive recovery
@@ -141,19 +141,19 @@ Before showing the recovery report, run a comprehensive diagnosis:
 2. **Scan all pipelines for failed/in-progress tasks**:
    ```bash
    # Feature pipeline
-   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 2>/dev/null
 
    # Bugfix pipeline
-   python3 dev-pipeline/scripts/update-bug-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-bug-status.py \
      --bug-list .prizmkit/plans/bug-fix-list.json \
      --state-dir .prizmkit/state/bugfix \
      --action status 2>/dev/null
 
    # Refactor pipeline
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status 2>/dev/null
@@ -259,7 +259,7 @@ AskUserQuestion:
   header: "Recovery"
   options:
     - label: "Run recovery script (Recommended)"
-      description: "Execute ./dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
+      description: "Execute ./.prizmkit/dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
     - label: "Copy command and run manually"
       description: "I'll give you the exact shell command to paste into your terminal — you run it yourself outside this session"
     - label: "Resume interactively in this session"
@@ -270,7 +270,7 @@ AskUserQuestion:
 
 **If "Run recovery script"** → Execute the pipeline recovery:
 ```bash
-./dev-pipeline/run-recovery.sh
+./.prizmkit/dev-pipeline/run-recovery.sh
 ```
 The script handles everything: detection, confirmation, prompt generation, session spawn, and post-session validation. **End this skill after launching the script** — do not proceed to Phase 2.
 
@@ -278,12 +278,12 @@ The script handles everything: detection, confirmation, prompt generation, sessi
 ```
 To recover, run this command in your project root:
 
-  ./dev-pipeline/run-recovery.sh
+  ./.prizmkit/dev-pipeline/run-recovery.sh
 
 Or with options:
-  ./dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
-  ./dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
-  ./dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
 ```
 **End this skill** — do not proceed to Phase 2. The user will run the command themselves.
 
@@ -312,7 +312,7 @@ End this skill.
    - If `context-snapshot.md` exists in the artifact directory → read it first. It provides a snapshot of completed tasks, key decisions, and remaining work from the interrupted session.
    - If `session-summary.md` exists → read it for a lightweight summary of the previous session.
    - Then read remaining artifacts: spec.md, plan.md, review-report.md, code diffs, bug descriptions, etc.
-3. **Read relevant `.prizm-docs/`** — load project context (L0 root, relevant L1/L2 for affected modules).
+3. **Read relevant `.prizmkit/prizm-docs/`** — load project context (L0 root, relevant L1/L2 for affected modules).
 
 This step replaces the context that was lost when the AI session was interrupted.
 

package/bundled/skills/recovery-workflow/scripts/detect-recovery-state.py

@@ -354,7 +354,6 @@ def detect_code_changes(project_root, main_branch="main"):
     # Note: .prizmkit/plans/*.json paths are caught by IGNORED_PREFIXES below
     IGNORED_PREFIXES = (
         ".prizmkit/",
-        ".prizm-docs/",
         ".claude/",
         ".codebuddy/",
     )

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -11,8 +11,8 @@ Launch the autonomous refactor pipeline from within an AI CLI conversation. The
 
 Three execution modes are available. The user chooses one before configuring other options:
 
-1. **Foreground** (recommended) — `dev-pipeline/run-refactor.sh run`. Visible output, direct error feedback, no orphaned processes.
-2. **Background daemon** — `dev-pipeline/launch-refactor-daemon.sh`. Runs fully detached, survives AI CLI session closure.
+1. **Foreground** (recommended) — `.prizmkit/dev-pipeline/run-refactor.sh run`. Visible output, direct error feedback, no orphaned processes.
+2. **Background daemon** — `.prizmkit/dev-pipeline/launch-refactor-daemon.sh`. Runs fully detached, survives AI CLI session closure.
 3. **Manual** — Display the assembled command(s) only. Do not execute anything. User runs them on their own.
 
 ### When to Use
@@ -45,7 +45,7 @@ Three execution modes are available. The user chooses one before configuring oth
 
 Before any action, validate:
 
-1. **refactor pipeline exists**: Confirm `dev-pipeline/launch-refactor-daemon.sh` and `dev-pipeline/run-refactor.sh` are present and executable
+1. **refactor pipeline exists**: Confirm `.prizmkit/dev-pipeline/launch-refactor-daemon.sh` and `.prizmkit/dev-pipeline/run-refactor.sh` are present and executable
 2. **For start**: `.prizmkit/plans/refactor-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
 4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
@@ -79,7 +79,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **Check not already running**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
    ```
    If running, inform user and ask: "Refactor pipeline is already running. Want to restart it, check status, or view logs?"
 
@@ -106,7 +106,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    If pipeline state already exists, use the status command instead:
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status 2>/dev/null
@@ -222,34 +222,34 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
    With all options:
    ```bash
    VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
-     dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+     .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
 
    **Background daemon command:**
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
    ```
    With all options:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json \
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json \
      --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 ENABLE_DEPLOY=1"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.
    ```
    # To run in foreground:
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
 
    # To run in background (detached):
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
 
    # To check status:
-   dev-pipeline/run-refactor.sh status .prizmkit/plans/refactor-list.json
+   .prizmkit/dev-pipeline/run-refactor.sh status .prizmkit/plans/refactor-list.json
    ```
 
 8. **Confirm and launch** (Foreground and Background only — Manual mode ends at step 7):
@@ -268,7 +268,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    **If background daemon**:
    1. Verify launch:
       ```bash
-      dev-pipeline/launch-refactor-daemon.sh status
+      .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
@@ -286,12 +286,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check daemon status**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
    ```
 
 2. **Show refactor-level progress**:
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status
@@ -310,12 +310,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Stop the daemon**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh stop
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh stop
    ```
 
 2. **Verify stopped**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null || true
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null || true
    ```
 
 3. **Inform user**: "Refactor pipeline stopped. State is preserved -- you can resume later with 'start refactoring' and it will pick up where it left off."
@@ -326,7 +326,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check if running**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
    ```
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
@@ -354,7 +354,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry R-001" or "clean retry R-001":
 
 ```bash
-dev-pipeline/reset-refactor.sh R-001 --clean --run .prizmkit/plans/refactor-list.json
+.prizmkit/dev-pipeline/reset-refactor.sh R-001 --clean --run .prizmkit/plans/refactor-list.json
 ```
 
 Notes:
@@ -376,11 +376,11 @@ Notes:
 | PID file stale (process dead) | `launch-refactor-daemon.sh` auto-cleans, retry start |
 | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/refactor/pipeline-daemon.log` |
 | Refactor stuck/blocked | Use `reset-refactor.sh <R-XXX> --clean --run` for a fresh retry |
-| All refactors blocked/failed | Show status, suggest recovery: `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
+| All refactors blocked/failed | Show status, suggest recovery: `.prizmkit/dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
 | `playwright-cli` not installed | Browser verification skipped for playwright refactors (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
 | `opencli` not installed | Browser verification skipped for opencli refactors (non-blocking). Install opencli for Chrome session-based browser verification |
 | Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/refactor/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
-| Permission denied on script | Run `chmod +x dev-pipeline/launch-refactor-daemon.sh dev-pipeline/run-refactor.sh` |
+| Permission denied on script | Run `chmod +x .prizmkit/dev-pipeline/launch-refactor-daemon.sh .prizmkit/dev-pipeline/run-refactor.sh` |
 
 ### Integration Notes
 

package/bundled/skills/refactor-planner/SKILL.md

@@ -92,11 +92,11 @@ Do NOT use this skill when the user wants to:
 ## Prerequisites
 
 Before questions, check optional context files (never block if absent):
-- `.prizm-docs/root.prizm` (architecture/project context)
+- `.prizmkit/prizm-docs/root.prizm` (architecture/project context)
 - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
 - Existing test suite (critical for behavior preservation assessment)
 - Existing `.prizmkit/plans/refactor-list.json` (if appending additional items)
-- If `.prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure:
+- If `.prizmkit/prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure:
   ```bash
   find . -maxdepth 2 -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' -not -path '*/vendor/*' | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
   ```
@@ -132,7 +132,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
 
 **Goal**: Understand the current codebase structure and tech stack.
 
-1. Read `.prizm-docs/root.prizm` and relevant L1 docs
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1 docs
 2. Read `.prizmkit/config.json` for tech stack info
 3. Identify existing test suite and coverage
 4. Summarize project context to the user: "Here's what I found about your project..."
@@ -142,7 +142,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
    > "Do you have any reference materials I should review before planning the refactoring? This can include:
    > - **Code paths** — specific files or directories that are refactoring targets or dependencies
    > - **Documents** — design docs, architecture proposals, refactoring RFCs, or technical debt analyses
-   > - **Knowledge docs** — `.prizm-docs/` files, README files, or internal wiki pages for the affected area
+   > - **Knowledge docs** — `.prizmkit/prizm-docs/` files, README files, or internal wiki pages for the affected area
    > - **Images** — architecture diagrams, dependency graphs, or whiteboard photos
    > - **Web links** — reference implementations, design pattern articles, or migration guides
    >
@@ -307,7 +307,7 @@ If issues found, discuss with user and resolve before proceeding.
 
 | Checkpoint | Artifact/State | Criteria | Phase |
 |-----------|----------------|----------|-------|
-| **CP-RP-0** | Project Context | Tech stack, test suite status, .prizm-docs loaded | 1 |
+| **CP-RP-0** | Project Context | Tech stack, test suite status, .prizmkit/prizm-docs loaded | 1 |
 | **CP-RP-1** | Goals Collected | All refactoring goals understood, no open ambiguities | 2 |
 | **CP-RP-2** | Code Analyzed | Analysis complete, user agrees with approach | 3 |
 | **CP-RP-3** | Items Decomposed | All items have deps, complexity, preservation strategy | 4 |
@@ -324,7 +324,7 @@ If issues found, discuss with user and resolve before proceeding.
 - Non-empty `refactors` array
 - Sequential IDs: `R-001`, `R-002`, ...
 - Valid dependency DAG (no cycles)
-- Each item has a declared `behavior_preservation` object with `strategy` field: `"test-gate"`, `"snapshot"`, or `"manual"`. Optional fields: `existing_tests` (boolean), `new_tests_needed` (string array). See `dev-pipeline/templates/refactor-list-schema.json` for the full schema.
+- Each item has a declared `behavior_preservation` object with `strategy` field: `"test-gate"`, `"snapshot"`, or `"manual"`. Optional fields: `existing_tests` (boolean), `new_tests_needed` (string array). See `.prizmkit/dev-pipeline/templates/refactor-list-schema.json` for the full schema.
 - `priority` must be a string: `"critical"`, `"high"`, `"medium"`, or `"low"`
 - New items default `status: "pending"`
 - English titles for stable slug generation

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

@@ -132,7 +132,7 @@ Then ask:
 Ask:
 1. **Code paths** — "Which files or directories are the main targets? Any specific files I should look at?"
 2. **Design documents** — "Do you have any design docs, architecture diagrams, or refactoring proposals I should read?"
-3. **Knowledge docs** — "Are there related `.prizm-docs/`, README files, or internal wiki pages for the target area?"
+3. **Knowledge docs** — "Are there related `.prizmkit/prizm-docs/`, README files, or internal wiki pages for the target area?"
 4. **Related issues/PRs** — "Any related issues, PRs, or previous refactoring attempts I should be aware of?"
 
 Record everything the user provides — these become inputs for Step 1.3.
@@ -147,7 +147,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 |-------|-------------|---------|
 | Agent A | User-provided code paths — read full source files | Understand current structure, interfaces, dependencies |
 | Agent B | User-provided documents — design docs, proposals, wiki pages | Understand intended direction and constraints |
-| Agent C | `.prizm-docs/` for affected modules — L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
+| Agent C | `.prizmkit/prizm-docs/` for affected modules — L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
 | Agent D | Test files for the target area — find and read existing tests | Understand current test coverage and behavior contracts |
 
 **Also gather** (can be included in any agent's task):
@@ -164,7 +164,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 Present what you learned from the parallel reading:
 - Current code structure and its problems (with specific file/function references)
 - Existing test coverage status (which areas are safe, which are risky)
-- Known TRAPS and pitfalls from `.prizm-docs/`
+- Known TRAPS and pitfalls from `.prizmkit/prizm-docs/`
 - Dependencies and potential impact on other modules
 
 Then ask targeted questions based on what you read. **Adapt question depth to the refactoring complexity** — a simple extract-method refactor needs fewer questions than a full module decomposition.
@@ -184,7 +184,7 @@ Then ask targeted questions based on what you read. **Adapt question depth to th
 - Any undocumented behavior that callers depend on?
 
 **Risk Assessment:**
-- "I found these TRAPS in .prizm-docs/: [list]. Any other known gotchas?"
+- "I found these TRAPS in .prizmkit/prizm-docs/: [list]. Any other known gotchas?"
 - Does this code have external consumers (other teams, published APIs)?
 - Any concurrent development happening in the target area?
 
@@ -249,7 +249,7 @@ Once brainstorming is complete, produce a structured goals summary:
 - [Risk]: [Mitigation strategy]
 
 ### 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]
 
 ### Constraints
 - [Timeline, coordination, deployment concerns]
@@ -293,7 +293,7 @@ AskUserQuestion:
   2. Invoke `/prizmkit-implement` to execute the plan (behavior preservation verified by tests)
   3. After implementation, run `/prizmkit-code-review` for quality check
   4. Commit via `/prizmkit-committer` with `refactor(<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 refactor list** → Continue to Phase 2 (Plan via pipeline)
 
@@ -394,7 +394,7 @@ AskUserQuestion:
 
 1. **Initial status check**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
    ```
 
 2. **Offer monitoring options**:
@@ -404,7 +404,7 @@ AskUserQuestion:
 
 3. **Periodic progress reports** (when user asks):
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status
@@ -480,4 +480,4 @@ While the pipeline runs, the user can continue the conversation:
 - Pipeline execution (Phase 3)
 - Progress updates (Phase 4)
 - Multiple git commits with `refactor(<scope>):` prefix
-- Updated `.prizm-docs/` (via prizmkit-retrospective per refactor item)
+- Updated `.prizmkit/prizm-docs/` (via prizmkit-retrospective per refactor item)

package/bundled/team/prizm-dev-team.json

@@ -13,7 +13,7 @@
       "name": "dev",
       "role": "developer", 
       "agentDefinition": "prizm-dev-team-dev",
-      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizm-docs/ TRAPS before implementing.",
+      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizmkit/prizm-docs/ TRAPS before implementing.",
       "subscriptions": ["*"]
     },
     {

package/bundled/templates/hooks/commit-intent.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "SRC=$(git diff --cached --name-only 2>/dev/null | grep -cE '\\.(ts|tsx|js|jsx|py|go|rs|java)$'); if [ \"$SRC\" -gt 0 ]; then PRIZM=$(git diff --cached --name-only 2>/dev/null | grep -c '^\\.prizm-docs/'); if [ \"$PRIZM\" -gt 0 ]; then echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ updated ($PRIZM file(s))\"; else echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ NOT UPDATED — update if this is a feature change\"; fi; fi"
+            "command": "SRC=$(git diff --cached --name-only 2>/dev/null | grep -cE '\\.(ts|tsx|js|jsx|py|go|rs|java)$'); if [ \"$SRC\" -gt 0 ]; then PRIZM=$(git diff --cached --name-only 2>/dev/null | grep -c '^\\.prizmkit/prizm-docs/'); if [ \"$PRIZM\" -gt 0 ]; then echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizmkit/prizm-docs/ updated ($PRIZM file(s))\"; else echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizmkit/prizm-docs/ NOT UPDATED — update if this is a feature change\"; fi; fi"
           }
         ]
       }
@@ -17,7 +17,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "TOOL_INPUT=\"${CLAUDE_TOOL_INPUT:-${CODEBUDDY_TOOL_INPUT:-}}\"; if echo \"$TOOL_INPUT\" | grep -qE 'git (commit|merge|rebase)' 2>/dev/null; then DRIFT=$(sh .prizmkit/scripts/diff-prizm-docs.sh 2>/dev/null); if [ -n \"$DRIFT\" ]; then echo \"PRIZMKIT_DRIFT_DETECTED: prizm-docs structural differences found:\"; echo \"$DRIFT\"; echo \"Please update affected .prizm-docs/ files.\"; fi; fi"
+            "command": "TOOL_INPUT=\"${CLAUDE_TOOL_INPUT:-${CODEBUDDY_TOOL_INPUT:-}}\"; if echo \"$TOOL_INPUT\" | grep -qE 'git (commit|merge|rebase)' 2>/dev/null; then DRIFT=$(sh .prizmkit/scripts/diff-prizm-docs.sh 2>/dev/null); if [ -n \"$DRIFT\" ]; then echo \"PRIZMKIT_DRIFT_DETECTED: prizm-docs structural differences found:\"; echo \"$DRIFT\"; echo \"Please update affected .prizmkit/prizm-docs/ files.\"; fi; fi"
           }
         ]
       }