prizmkit 1.0.45 → 1.0.66

package/bundled/dev-pipeline/tests/test_utils.py

@@ -1,141 +1,82 @@
-"""Tests for utils.py."""
+"""Tests for dev-pipeline/scripts/utils.py shared utilities."""
 
 import json
 import os
-import pytest
+import tempfile
 
 from utils import load_json_file, write_json_file, pad_right, _build_progress_bar
 
 
-class TestLoadJsonFile:
-    def test_valid_json(self, tmp_path):
-        p = tmp_path / "valid.json"
-        p.write_text('{"key": "value"}', encoding="utf-8")
-        data, err = load_json_file(str(p))
-        assert err is None
-        assert data == {"key": "value"}
-
-    def test_invalid_json(self, tmp_path):
-        p = tmp_path / "invalid.json"
-        p.write_text("{not valid json", encoding="utf-8")
-        data, err = load_json_file(str(p))
-        assert data is None
-        assert "Invalid JSON" in err
-
-    def test_missing_file(self, tmp_path):
-        data, err = load_json_file(str(tmp_path / "missing.json"))
-        assert data is None
-        assert "File not found" in err
-
-    def test_empty_file(self, tmp_path):
-        p = tmp_path / "empty.json"
-        p.write_text("", encoding="utf-8")
-        data, err = load_json_file(str(p))
-        assert data is None
-        assert "Invalid JSON" in err
-
-    def test_unicode_content(self, tmp_path):
-        p = tmp_path / "unicode.json"
-        p.write_text('{"name": "hello"}', encoding="utf-8")
-        data, err = load_json_file(str(p))
-        assert err is None
-        assert data["name"] == "hello"
+# ---------------------------------------------------------------------------
+# load_json_file / write_json_file round-trip
+# ---------------------------------------------------------------------------
 
-    def test_nested_json(self, tmp_path):
-        nested = {"a": {"b": [1, 2, 3]}}
-        p = tmp_path / "nested.json"
-        p.write_text(json.dumps(nested), encoding="utf-8")
-        data, err = load_json_file(str(p))
+class TestJsonIO:
+    def test_round_trip(self, tmp_path):
+        path = str(tmp_path / "data.json")
+        data = {"features": [{"id": "F-001"}]}
+        err = write_json_file(path, data)
         assert err is None
-        assert data == nested
 
-
-class TestWriteJsonFile:
-    def test_write_and_read_back(self, tmp_path):
-        p = str(tmp_path / "output.json")
-        data = {"hello": "world", "num": 42}
-        err = write_json_file(p, data)
+        loaded, err = load_json_file(path)
         assert err is None
-        read_data, read_err = load_json_file(p)
-        assert read_err is None
-        assert read_data == data
-
-    def test_creates_parent_directories(self, tmp_path):
-        p = str(tmp_path / "a" / "b" / "c" / "output.json")
-        err = write_json_file(p, {"nested": True})
+        assert loaded == data
+
+    def test_load_missing_file(self):
+        loaded, err = load_json_file("/nonexistent/path.json")
+        assert loaded is None
+        assert "not found" in err.lower() or "File not found" in err
+
+    def test_load_invalid_json(self, tmp_path):
+        path = str(tmp_path / "bad.json")
+        with open(path, "w") as f:
+            f.write("{invalid json}")
+        loaded, err = load_json_file(path)
+        assert loaded is None
+        assert "invalid" in err.lower() or "Invalid" in err
+
+    def test_write_creates_parent_dirs(self, tmp_path):
+        path = str(tmp_path / "a" / "b" / "c" / "data.json")
+        err = write_json_file(path, {"ok": True})
         assert err is None
-        assert os.path.isfile(p)
-
-    def test_overwrites_existing(self, tmp_path):
-        p = str(tmp_path / "overwrite.json")
-        write_json_file(p, {"v": 1})
-        write_json_file(p, {"v": 2})
-        data, _ = load_json_file(p)
-        assert data["v"] == 2
-
-    def test_unicode_data(self, tmp_path):
-        p = str(tmp_path / "unicode.json")
-        err = write_json_file(p, {"name": "hello"})
-        assert err is None
-        data, _ = load_json_file(p)
-        assert data["name"] == "hello"
+        assert os.path.isfile(path)
+
 
+# ---------------------------------------------------------------------------
+# pad_right
+# ---------------------------------------------------------------------------
 
 class TestPadRight:
-    def test_shorter_than_width(self):
+    def test_basic_padding(self):
         result = pad_right("abc", 10)
         assert len(result) == 10
         assert result == "abc       "
 
-    def test_exact_width(self):
-        result = pad_right("abcde", 5)
-        assert result == "abcde"
-
-    def test_longer_than_width(self):
-        result = pad_right("abcdefgh", 5)
-        assert result == "abcdefgh"
+    def test_no_padding_needed(self):
+        result = pad_right("abcdef", 3)
+        assert result == "abcdef"
 
-    def test_empty_string(self):
-        result = pad_right("", 5)
-        assert result == "     "
+    def test_ansi_escape_ignored(self):
+        # ANSI color code should not count toward visible length
+        text = "\033[31mred\033[0m"  # "red" with ANSI color (3 visible chars)
+        result = pad_right(text, 10)
+        # Visible length is 3, so 7 spaces of padding
+        assert result.endswith("       ")
 
-    def test_ansi_codes_ignored(self):
-        # ANSI escape should not count toward visible length
-        text = "\033[92mHi\033[0m"  # visible "Hi" = 2 chars
-        result = pad_right(text, 5)
-        # visible width is 2, so 3 spaces of padding
-        assert result.endswith("   ")
-
-    def test_zero_width(self):
-        result = pad_right("abc", 0)
-        assert result == "abc"
 
+# ---------------------------------------------------------------------------
+# _build_progress_bar
+# ---------------------------------------------------------------------------
 
 class TestBuildProgressBar:
     def test_zero_percent(self):
-        bar = _build_progress_bar(0)
+        bar = _build_progress_bar(0, width=10)
         assert "0%" in bar
-        assert "\u2591" in bar  # empty blocks
-        assert "\u2588" not in bar  # no filled blocks
-
-    def test_fifty_percent(self):
-        bar = _build_progress_bar(50, width=20)
-        assert "50%" in bar
-        assert bar.count("\u2588") == 10
-        assert bar.count("\u2591") == 10
 
     def test_hundred_percent(self):
-        bar = _build_progress_bar(100, width=20)
+        bar = _build_progress_bar(100, width=10)
         assert "100%" in bar
-        assert bar.count("\u2588") == 20
-        assert bar.count("\u2591") == 0
 
-    def test_custom_width(self):
+    def test_fifty_percent(self):
         bar = _build_progress_bar(50, width=10)
-        assert bar.count("\u2588") == 5
-        assert bar.count("\u2591") == 5
-
-    def test_partial_percent(self):
-        bar = _build_progress_bar(33, width=10)
-        assert bar.count("\u2588") == 3
-        assert bar.count("\u2591") == 7
+        assert "50%" in bar

package/bundled/rules/prizm/prizm-commit-workflow.md

@@ -3,8 +3,8 @@ description: "PrizmKit commit workflow rules"
 ---
 
 Before any git commit in this project:
-1. Update `.prizm-docs/` for affected modules
+1. Run `/prizmkit-retrospective` to sync `.prizm-docs/` (memory maintenance)
 2. Use Conventional Commits format: type(scope): description
 3. Bug fixes use `fix()` prefix, not `feat()`
-4. Do NOT create REGISTRY.md entries for bug fixes
-5. Use `/prizmkit-committer` command for the complete commit workflow
+4. Bug fixes run retrospective with structural sync only (Job 1)
+5. Use `/prizmkit-committer` command for the pure commit workflow

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.45",
+  "version": "1.0.66",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -23,7 +23,7 @@
       "hasScripts": false
     },
     "prizmkit-clarify": {
-      "description": "Interactive requirement clarification. Resolves ambiguities in feature specs.",
+      "description": "Interactive requirement clarification. Resolves ambiguities in feature specs. Use when spec has unclear parts or you're unsure about requirements before planning.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": false,
@@ -37,7 +37,7 @@
       "hasScripts": false
     },
     "prizmkit-analyze": {
-      "description": "Cross-document consistency analysis for spec.md and plan.md (including Tasks section).",
+      "description": "Cross-document consistency analysis for spec.md and plan.md. Check if spec and plan are aligned, validate documents before coding.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": false,
@@ -58,24 +58,17 @@
       "hasScripts": false
     },
     "prizmkit-committer": {
-      "description": "Commit workflow with automatic Prizm doc updates and changelog management.",
+      "description": "Pure git commit workflow with safety checks. Does NOT modify .prizm-docs/.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": false,
       "hasScripts": false
     },
-    "prizmkit-summarize": {
-      "description": "Archive completed features to REGISTRY.md.",
-      "tier": "1",
-      "category": "prizmkit-skill",
-      "hasAssets": true,
-      "hasScripts": false
-    },
     "prizmkit-retrospective": {
-      "description": "Post-feature retrospective. Extracts lessons from completed features.",
+      "description": "Sole .prizm-docs/ maintainer. Update project documentation after code changes. Structural sync + knowledge injection (TRAPS/RULES/DECISIONS). Run after code review passes, before committing.",
       "tier": "1",
       "category": "prizmkit-skill",
-      "hasAssets": false,
+      "hasAssets": true,
       "hasScripts": false
     },
     "prizmkit-prizm-docs": {
@@ -224,6 +217,13 @@
       "category": "Custom-skill",
       "hasAssets": false,
       "hasScripts": false
+    },
+    "bug-fix-workflow": {
+      "description": "Interactive single-bug fix in current session. Guides triage → reproduce → fix → review → commit without background pipeline.",
+      "tier": "companion",
+      "category": "Custom-skill",
+      "hasAssets": false,
+      "hasScripts": false
     }
   },
   "suites": {
@@ -244,14 +244,14 @@
         "prizmkit-implement",
         "prizmkit-code-review",
         "prizmkit-committer",
-        "prizmkit-summarize",
         "prizmkit-retrospective",
         "feature-workflow",
         "refactor-workflow",
         "app-planner",
         "bug-planner",
         "dev-pipeline-launcher",
-        "bugfix-pipeline-launcher"
+        "bugfix-pipeline-launcher",
+        "bug-fix-workflow"
       ]
     },
     "minimal": {
@@ -267,7 +267,6 @@
         "prizmkit-implement",
         "prizmkit-code-review",
         "prizmkit-committer",
-        "prizmkit-summarize",
         "prizmkit-retrospective"
       ]
     }

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

@@ -92,7 +92,7 @@ Execute the selected scenario workflow in conversation mode with mandatory check
 
 ### Checkpoints (Mandatory Gates)
 
-Never skip checkpoints. If any checkpoint fails, follow error recovery flow (see §Error Recovery).
+Checkpoints catch cascading errors early — skipping one means the next phase builds on unvalidated assumptions, which compounds into much harder debugging later.
 
 | Checkpoint | Artifact/State | Criteria | Phase |
 |-----------|----------------|----------|-------|
@@ -311,16 +311,17 @@ Resume incremental planning? (Y/n)"
 
 ### Artifact Path Convention
 
-Recommended structure for feature planning artifacts:
+The primary output `feature-list.json` is always written to the **project root** — this is where `dev-pipeline-launcher` and all pipeline scripts expect it.
 
 ```
-.prizmkit/planning/
-  ├── feature-list.json              # Primary output (always here)
-  ├── feature-list.validated.json    # Checkpoint backup after CP-AP-5
-  └── <ISO-timestamp>.backup.json    # Optional incremental backups
+<project-root>/
+  ├── feature-list.json              # Primary output (always here, at project root)
+  └── .prizmkit/planning/            # Optional organization for backups
+      ├── feature-list.validated.json    # Checkpoint backup after CP-AP-5
+      └── <ISO-timestamp>.backup.json    # Optional incremental backups
 ```
 
-Mention this path when summarizing (Phase 8 handoff) to help users organize future sessions.
+The pipeline reads `feature-list.json` from the project root by default. If the user specifies a custom path, the launcher accepts it as an argument.
 
 Maintainer note: evaluation workflow moved to `assets/evaluation-guide.md`.
 

package/bundled/skills/bug-fix-workflow/SKILL.md

@@ -0,0 +1,171 @@
+---
+name: "bug-fix-workflow"
+tier: companion
+description: "Interactive single-bug fix in current session. Guides through triage → reproduce → fix → review → commit without the background pipeline. Use this skill when the user wants to fix one specific bug right now, interactively. Trigger on: 'fix this bug', 'debug this', 'fix B-001', 'help me fix', 'let me fix this bug myself', '修这个 bug', '交互式修复', '手动修 bug'. (project)"
+---
+
+# Bug Fix Workflow
+
+Fix a single bug interactively within the current AI CLI session. This is the in-session counterpart to `bugfix-pipeline-launcher` (which runs multiple bugs in the background).
+
+## When to Use
+
+- User wants to fix **one specific bug** right now, with full visibility
+- User says "fix this bug", "debug this error", "help me fix B-001", "修这个 bug"
+- User has a stack trace or error and wants interactive debugging
+- User prefers hands-on fixing over background pipeline
+
+**Do NOT use when:**
+- User has multiple bugs to fix in batch → `bug-planner` + `bugfix-pipeline-launcher`
+- User wants to plan/collect bugs without fixing → `bug-planner`
+- User wants background autonomous fixing → `bugfix-pipeline-launcher`
+- User wants to build features → `feature-workflow`
+
+## Input
+
+The bug can come from:
+- **A bug-fix-list.json entry**: "fix B-001" → read the entry from bug-fix-list.json
+- **A stack trace/error message**: user pastes error directly
+- **A description**: "the login page crashes when I click submit"
+- **A failed test**: "this test is failing: src/auth/__tests__/login.test.ts"
+
+## Execution
+
+### Phase 1: Triage
+
+**Goal**: Understand the bug, locate affected code, classify severity.
+
+1. **Gather bug info**:
+   - If bug ID given (e.g. B-001): read entry from `bug-fix-list.json`
+   - If raw error: extract error message, stack trace, affected files
+   - If description: ask clarifying questions to narrow down the issue
+2. **Read project context**: `.prizm-docs/root.prizm` → relevant L1/L2 docs for affected modules
+3. **Locate affected code**: read the files mentioned in the error/stack trace
+4. **Check known issues**: search `.prizm-docs/` TRAPS sections for matching patterns
+5. **Classify**: root cause (confirmed/suspected), blast radius, fix complexity
+6. **Present diagnosis to user**:
+   ```
+   Bug: Login page crash on submit
+   Root Cause: AuthService.handleLogin() receives null token when API returns 401
+   Affected Files: src/services/auth.ts (L42), src/pages/login.tsx (L28)
+   Fix Complexity: Low (null check + error handling)
+   ```
+   Ask: "Does this diagnosis look right? Should I proceed with the fix?"
+
+### Phase 2: Reproduce
+
+**Goal**: Create a failing test that proves the bug exists.
+
+1. **Write a reproduction test** that demonstrates the bug:
+   - Name: `<module>.test.ts` → add a test case named `should handle <bug scenario>`
+   - The test captures the exact failure condition
+2. **Run the test** → confirm it **fails** (red)
+3. **Show result to user**: "Reproduction test written and confirmed failing."
+
+If the bug is hard to reproduce automatically (e.g. environment-specific):
+- Ask the user for reproduction steps
+- Write a manual reproduction checklist instead
+- Proceed to Phase 3 with the manual checklist
+
+### Phase 3: Fix
+
+**Goal**: Implement the minimal fix. Red test → green.
+
+1. **Implement the fix**:
+   - Change the minimum amount of code to fix the root cause
+   - Do NOT refactor or add unrelated improvements — fix the bug only
+   - Follow existing code conventions (read from `.prizm-docs/` RULES/PATTERNS)
+2. **Run the reproduction test** → must **pass** (green)
+3. **Run the full module test suite** → must pass (no regressions)
+4. **Show the fix to user**:
+   - Summary of changes made
+   - Test results (reproduction + regression)
+   - Ask: "Fix looks good? Any concerns?"
+
+If the fix causes test regressions:
+- Show which tests broke and why
+- Revise the fix (max 3 attempts)
+- If still failing after 3 attempts, escalate to user with analysis
+
+### Phase 4: Review
+
+**Goal**: Verify fix quality before committing.
+
+1. **Self-review** the changes:
+   - Does the fix address the root cause (not just the symptom)?
+   - Are there edge cases not covered?
+   - Is the reproduction test thorough enough?
+   - Does the fix follow project conventions?
+2. **Run full test suite** one final time
+3. **Present review summary**:
+   ```
+   Fix Review:
+   - Root cause addressed: Yes (null check added at auth service level)
+   - Edge cases: Covered (401, 403, network error)
+   - Regression: None (48/48 tests pass)
+   - Code quality: Clean, follows existing patterns
+
+   Ready to commit.
+   ```
+
+### Phase 5: Commit
+
+**Goal**: Commit the fix with proper conventions.
+
+1. **Run `/prizmkit-committer`**:
+   - Commit message: `fix(<scope>): <description>`
+   - Include both fix code and reproduction test
+   - Do NOT push (user decides when to push)
+   - Do NOT run `/prizmkit-retrospective` — bug fixes do not update `.prizm-docs/` (per project rules: "bugs are incomplete features, recording bug details causes doc bloat with no AI value")
+   - `/prizmkit-committer` is a pure commit tool — it does NOT modify `.prizm-docs/` or any project files
+2. **If bug came from bug-fix-list.json**: inform user to update bug status
+   ```
+   Bug B-001 fixed and committed.
+   To update the bug list: manually set B-001 status to "fixed" in bug-fix-list.json
+   Or retry the pipeline to pick up remaining bugs.
+   ```
+
+## Artifacts
+
+Bug fix artifacts are stored at `.prizmkit/bugfix/<BUG_ID>/`:
+- `fix-plan.md` — Triage output (diagnosis, root cause, fix approach)
+- `fix-report.md` — Post-fix summary (what changed, test results, TRAPS added)
+
+Only 2 artifact files per bug, consistent with the pipeline convention.
+
+## Comparison with Pipeline Bug Fix
+
+| Dimension | bug-fix-workflow (this skill) | bugfix-pipeline-launcher |
+|-----------|-------------------------------|--------------------------|
+| Scope | One bug at a time | All bugs in batch |
+| Execution | Interactive, in-session | Background daemon |
+| Visibility | Full user interaction at each phase | Async, check status periodically |
+| Best for | Complex bugs needing user input | Batch of well-defined bugs |
+| Artifacts | Same (fix-plan.md + fix-report.md) | Same |
+| Commit prefix | `fix(<scope>):` | `fix(<scope>):` |
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| Bug ID not found in bug-fix-list.json | Ask user to provide bug details directly |
+| Cannot reproduce the bug | Ask for more context, try alternative reproduction |
+| Fix causes regressions | Revert, analyze, retry (max 3 rounds) |
+| Root cause unclear after investigation | Present findings, ask user for guidance |
+| Affected files are in unfamiliar module | Read `.prizm-docs/` L1/L2 for that module first |
+
+## HANDOFF
+
+| From | To | Condition |
+|------|----|-----------|
+| `bug-planner` | **this skill** | User picks one bug to fix interactively |
+| `bugfix-pipeline-launcher` | **this skill** | User wants to fix a stuck/complex bug manually |
+| **this skill** | `bugfix-pipeline-launcher` | After fixing, user wants to continue with remaining bugs |
+| **this skill** | `prizmkit-committer` | Built into Phase 5 (pure commit, no doc sync) |
+
+## Output
+
+- Fixed code with reproduction test
+- `.prizmkit/bugfix/<BUG_ID>/fix-plan.md`
+- `.prizmkit/bugfix/<BUG_ID>/fix-report.md`
+- Git commit with `fix(<scope>):` prefix

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

@@ -1,7 +1,7 @@
 ---
 name: "bug-planner"
 tier: companion
-description: "Interactive bug planning that produces bug-fix-list.json for the Bug Fix Pipeline. Supports multiple input formats: error logs, stack traces, user reports, failed tests, monitoring alerts. (project)"
+description: "Interactive bug planning that produces bug-fix-list.json for the Bug Fix Pipeline. Supports multiple input formats: error logs, stack traces, user reports, failed tests, monitoring alerts. Use this skill whenever the user has bugs to report, errors to parse, or test failures to organize. Trigger on: 'plan bug fixes', 'report bugs', 'I have some bugs', 'these tests are failing', 'here is an error log', 'parse these errors', '修复 bug', '生成 bug 列表', '规划 bug 修复'. (project)"
 ---
 
 # Bug Planner
@@ -17,33 +17,28 @@ User says:
 - "here's an error log", "parse these errors"
 - After receiving bug reports, error logs, or failed test output
 
-## Commands
+**Do NOT use when:**
+- User wants to start fixing bugs now (use `bugfix-pipeline-launcher`)
+- User wants to fix a single bug interactively (use `bug-fix-workflow`)
+- User wants to plan features (use `app-planner`)
 
-### prizmkit.bug-plan
+## Intent Routing
 
-Launch the interactive bug planning process.
+This skill handles multiple operations. Determine the user's intent and execute the matching operation:
 
-### prizmkit.bug-plan-from-log \<log-file-or-content\>
-
-Auto-generate bug entries from error logs or stack traces.
-
-### prizmkit.bug-plan-from-tests \<test-output\>
-
-Auto-generate bug entries from failed test case output.
-
-### prizmkit.bug-plan-validate \<bug-fix-list.json\>
-
-Validate an existing `bug-fix-list.json` against the schema.
-
-### prizmkit.bug-plan-summary \<bug-fix-list.json\>
-
-Print a summary of bugs grouped by severity and status.
+| User Intent | Operation | Trigger Phrases |
+|---|---|---|
+| Plan bugs interactively | **Interactive Planning** | "plan bug fixes", "report bugs", "规划 bug 修复" |
+| Parse error logs into bugs | **From Log** | "parse this error log", "here's a stack trace", "parse these errors" |
+| Parse test failures into bugs | **From Tests** | "these tests are failing", "parse test output" |
+| Validate existing bug list | **Validate** | "validate bug list", "check bug-fix-list.json" |
+| Summarize bug list | **Summary** | "bug summary", "show bug list", "list bugs" |
 
 ---
 
-## Interactive Planning Process
+## Operation: Interactive Planning
 
-The interactive `prizmkit.bug-plan` command guides through 4 phases:
+Launch the interactive bug planning process through 4 phases.
 
 ### Phase 1: Project Context
 
@@ -140,7 +135,11 @@ ALERT: Error rate spike: 500 errors/min on /api/login endpoint
 ### Phase 4: Generate & Validate
 
 1. **Generate `bug-fix-list.json`**: Conform to `dev-pipeline/templates/bug-fix-list-schema.json`
-2. **Validate against schema**: Run the validation checks below
+2. **Validate against schema**: Run the validation script:
+   ```bash
+   python3 ${SKILL_DIR}/scripts/validate-bug-list.py bug-fix-list.json --feature-list feature-list.json
+   ```
+   If the script is not available, perform the validation checks manually (see checklist below).
 3. **Write file** to project root (or user-specified path)
 4. **Output**: File path, summary, and next steps
 
@@ -179,14 +178,11 @@ Next steps:
 - Review: cat bug-fix-list.json
 - Start fixing: say "开始修复" or "start fixing bugs" to launch the bugfix pipeline
 - Or run directly: ./dev-pipeline/launch-bugfix-daemon.sh start bug-fix-list.json
-- Fix one interactively: invoke bug-fix-workflow for each bug
 ```
 
 ---
 
-## Non-Interactive Commands
-
-### prizmkit.bug-plan-from-log
+## Operation: From Log
 
 Batch-parse error logs to generate bug entries without interactive prompts:
 
@@ -202,7 +198,7 @@ Batch-parse error logs to generate bug entries without interactive prompts:
 4. Output draft `bug-fix-list.json` for user review
 5. Ask: "Review and confirm? You can edit individual entries."
 
-### prizmkit.bug-plan-from-tests
+## Operation: From Tests
 
 Batch-parse failed test output:
 
@@ -212,7 +208,7 @@ Batch-parse failed test output:
 4. Set verification_type to `automated` (test already exists)
 5. Output draft `bug-fix-list.json`
 
-### prizmkit.bug-plan-validate
+## Operation: Validate
 
 Validate existing `bug-fix-list.json`:
 
@@ -226,7 +222,7 @@ Validate existing `bug-fix-list.json`:
    - Invalid `affected_feature` references (if feature-list.json exists)
 4. Output: validation result with specific errors/warnings
 
-### prizmkit.bug-plan-summary
+## Operation: Summary
 
 Print human-readable summary:
 
@@ -269,10 +265,6 @@ After `bug-fix-list.json` is generated, the user can:
 | Invalid feature reference | Warn and ask user to correct or remove reference |
 | Schema validation failure | Show specific errors, offer to fix interactively |
 
-## Path References
-
-All internal asset paths MUST use `${SKILL_DIR}` placeholder for cross-IDE compatibility.
-
 ## Output
 
 - `bug-fix-list.json` conforming to `dev-pipeline/templates/bug-fix-list-schema.json`