prizmkit 1.1.7 → 1.1.9

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

@@ -46,7 +46,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
-2. **For start**: `refactor-list.json` must exist in project root (or user-specified path)
+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
 
@@ -55,8 +55,8 @@ Quick check:
 command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
 ```
 
-If `refactor-list.json` is missing, inform user:
-> "No refactor-list.json found. Run the `refactor-planner` skill first to generate one, or provide a path to your refactor list."
+If `.prizmkit/plans/refactor-list.json` is missing, inform user:
+> "No .prizmkit/plans/refactor-list.json found. Run the `refactor-planner` skill first to generate one, or provide a path to your refactor list."
 
 ### Workflow
 
@@ -68,7 +68,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check prerequisites**:
    ```bash
-   ls refactor-list.json 2>/dev/null && echo "Found" || echo "Missing"
+   ls .prizmkit/plans/refactor-list.json 2>/dev/null && echo "Found" || echo "Missing"
    ```
 
 2. **Check not already running**:
@@ -81,7 +81,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```bash
    python3 -c "
    import json
-   with open('refactor-list.json') as f:
+   with open('.prizmkit/plans/refactor-list.json') as f:
        data = json.load(f)
    refactors = data.get('refactors', [])
    print(f'Total refactor tasks: {len(refactors)}')
@@ -101,8 +101,8 @@ 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 \
-     --refactor-list refactor-list.json \
-     --state-dir dev-pipeline/refactor-state \
+     --refactor-list .prizmkit/plans/refactor-list.json \
+     --state-dir .prizmkit/state/refactor \
      --action status 2>/dev/null
    ```
 
@@ -135,20 +135,16 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
 
-   **Question 1 — Critic review** (multiSelect: false):
-   - Off (default) — Skip adversarial review
-   - On — Enable critic review after refactoring (+3-8 min/refactor for critical/high complexity)
-
-   **Question 2 — Verbose logging** (multiSelect: false):
+   **Question 1 — Verbose logging** (multiSelect: false):
    - On (default) — Detailed AI session logs including tool calls and subagent activity
    - Off — Minimal logging
 
-   **Question 3 — Max retries** (multiSelect: false):
+   **Question 2 — Max retries** (multiSelect: false):
    - 3 (default)
    - 1
    - 5
 
-   **Question 4 — Session timeout** (multiSelect: false):
+   **Question 3 — Session timeout** (multiSelect: false):
    - None (default) — No timeout
    - 30 min — `SESSION_TIMEOUT=1800`
    - 1 hour — `SESSION_TIMEOUT=3600`
@@ -171,40 +167,53 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Strict behavior: On | `STRICT_BEHAVIOR_CHECK=1` |
    | Strict behavior: Off | `STRICT_BEHAVIOR_CHECK=0` |
 
+   **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
+
+   | Variable | Default | Purpose |
+   |----------|---------|---------|
+   | `MODEL` | (none) | AI model override (e.g. `claude-opus-4.6`) |
+   | `AUTO_PUSH` | `0` | Auto-push to remote after successful refactor (`1` to enable) |
+   | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `refactor/pipeline-{run_id}`) |
+   | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
+   | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
+   | `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
+   | `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
+   | `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
+
    ⚠️ STOP HERE and wait for user response before continuing to step 7.
 
 7. **Show final command**: After user confirms configuration in step 6, assemble the complete command from execution mode + user-confirmed configuration, and present it to the user.
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 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 \
-     dev-pipeline/run-refactor.sh run refactor-list.json
+     dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
 
    **Background daemon command:**
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh start refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   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 refactor-list.json \
+   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json \
      --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5"
    ```
 
    **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 refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
 
    # To run in background (detached):
-   dev-pipeline/launch-refactor-daemon.sh start refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   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 refactor-list.json
+   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):
@@ -227,7 +236,7 @@ Detect user intent from their message, then follow the corresponding workflow:
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
-      tail -f dev-pipeline/refactor-state/pipeline-daemon.log
+      tail -f .prizmkit/state/refactor/pipeline-daemon.log
       ```
    3. Report to user:
       - Pipeline PID
@@ -247,14 +256,14 @@ Detect user intent from their message, then follow the corresponding workflow:
 2. **Show refactor-level progress**:
    ```bash
    python3 dev-pipeline/scripts/update-refactor-status.py \
-     --refactor-list refactor-list.json \
-     --state-dir dev-pipeline/refactor-state \
+     --refactor-list .prizmkit/plans/refactor-list.json \
+     --state-dir .prizmkit/state/refactor \
      --action status
    ```
 
 3. **Show recent log activity** (last 20 lines):
    ```bash
-   tail -20 dev-pipeline/refactor-state/pipeline-daemon.log
+   tail -20 .prizmkit/state/refactor/pipeline-daemon.log
    ```
 
 4. **Summarize** to user: total refactors, completed, in-progress, failed, pending.
@@ -286,20 +295,20 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
    ```bash
-   tail -f dev-pipeline/refactor-state/pipeline-daemon.log
+   tail -f .prizmkit/state/refactor/pipeline-daemon.log
    ```
 
 3. **If not running** -- Show last 50 lines:
    ```bash
-   tail -50 dev-pipeline/refactor-state/pipeline-daemon.log
+   tail -50 .prizmkit/state/refactor/pipeline-daemon.log
    ```
 
 4. **For per-refactor session logs** (when user asks about a specific refactor):
    ```bash
    # Check refactor status for last session ID
-   cat dev-pipeline/refactor-state/refactors/<REFACTOR_ID>/status.json 2>/dev/null
+   cat .prizmkit/state/refactor/refactors/<REFACTOR_ID>/status.json 2>/dev/null
    # Then tail that refactor's session log
-   tail -100 dev-pipeline/refactor-state/refactors/<REFACTOR_ID>/sessions/<SESSION_ID>/logs/session.log
+   tail -100 .prizmkit/state/refactor/refactors/<REFACTOR_ID>/sessions/<SESSION_ID>/logs/session.log
    ```
 
 ---
@@ -309,23 +318,22 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry R-001":
 
 ```bash
-dev-pipeline/retry-refactor.sh R-001 refactor-list.json
+dev-pipeline/retry-refactor.sh R-001 .prizmkit/plans/refactor-list.json
 ```
 
 When user says "clean retry R-001" or "retry R-001 from scratch":
 
 ```bash
-dev-pipeline/reset-refactor.sh R-001 --clean --run refactor-list.json
+dev-pipeline/reset-refactor.sh R-001 --clean --run .prizmkit/plans/refactor-list.json
 ```
 
 Environment variables (optional):
 ```bash
-SESSION_TIMEOUT=3600 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/retry-refactor.sh R-001 refactor-list.json
+SESSION_TIMEOUT=3600 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/retry-refactor.sh R-001 .prizmkit/plans/refactor-list.json
 ```
 
 Notes:
-- `retry-refactor.sh` runs exactly one refactor session and exits.
-- `reset-refactor.sh --clean --run` clears the refactor state before retrying (fresh start).
+- `retry-refactor.sh` runs exactly one refactor session and exits. It **preserves prior session artifacts and checkpoint state** — reads `retry_count` and `resume_from_phase` from `status.json` so the AI session can resume from where it left off. For a full clean retry, use `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run`.
 - Keep pipeline daemon mode for main run management (`launch-refactor-daemon.sh`).
 
 ---
@@ -334,23 +342,23 @@ Notes:
 
 | Error | Action |
 |-------|--------|
-| `refactor-list.json` not found | Tell user to run `refactor-planner` skill first |
-| Circular dependencies in refactor list | Fix dependency graph in `refactor-list.json` before launching |
+| `.prizmkit/plans/refactor-list.json` not found | Tell user to run `refactor-planner` skill first |
+| Circular dependencies in refactor list | Fix dependency graph in `.prizmkit/plans/refactor-list.json` before launching |
 | Test baseline failing | Fix failing tests before starting refactoring -- behavior preservation requires a green baseline |
 | `jq` not installed | Suggest: `brew install jq` |
 | `cbc`/`claude` not in PATH | Check AI CLI installation |
 | Refactor pipeline already running | Show status, ask if user wants to stop and restart |
 | 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 dev-pipeline/refactor-state/pipeline-daemon.log` |
+| Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/refactor/pipeline-daemon.log` |
 | Refactor stuck/blocked | Use `retry-refactor.sh <R-XXX>` to retry; use `reset-refactor.sh <R-XXX> --clean --run` for fresh start |
-| All refactors blocked/failed | Show status, suggest recovery: `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run refactor-list.json` |
+| All refactors blocked/failed | Show status, suggest recovery: `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
 | Permission denied on script | Run `chmod +x dev-pipeline/launch-refactor-daemon.sh dev-pipeline/run-refactor.sh` |
 
 ### Integration Notes
 
-- **After refactor-planner**: This is the natural next step. When user finishes refactor planning and has `refactor-list.json`, suggest launching the refactor pipeline.
+- **After refactor-planner**: This is the natural next step. When user finishes refactor planning and has `.prizmkit/plans/refactor-list.json`, suggest launching the refactor pipeline.
 - **Session independence**: The pipeline runs completely detached. User can close the AI CLI session, open a new session later, and use this skill to check progress or stop the pipeline.
 - **Single instance**: Only one refactor pipeline can run at a time. The PID file prevents duplicates.
-- **Pipeline coexistence**: Refactor pipeline uses `refactor-state/` separate from `state/` (features) and `bugfix-state/` (bugs), so all three pipelines can run simultaneously without conflict.
+- **Pipeline coexistence**: Refactor pipeline uses `.prizmkit/state/refactor/` separate from `.prizmkit/state/features/` (features) and `.prizmkit/state/bugfix/` (bugs), so all three pipelines can run simultaneously without conflict.
 - **State preservation**: Stopping and restarting the pipeline resumes from where it left off -- completed refactors are not re-run.
 - **HANDOFF**: After pipeline completes all refactors, each session has already run `prizmkit-retrospective` internally. Ask user what's next.

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

@@ -1,6 +1,6 @@
 ---
 name: "refactor-planner"
-description: "Interactive refactoring planner. Understands refactoring intent through dialogue, analyzes current code structure, produces validated refactor-list.json for dev-pipeline execution. Use whenever users discuss refactoring planning, code restructuring scope, or preparing refactor-list.json."
+description: "Interactive refactoring planner. Understands refactoring intent through dialogue, analyzes current code structure, produces validated .prizmkit/plans/refactor-list.json for dev-pipeline execution. Use whenever users discuss refactoring planning, code restructuring scope, or preparing .prizmkit/plans/refactor-list.json."
 ---
 
 # refactor planner
@@ -9,7 +9,7 @@ Plan executable refactoring items for dev-pipeline:
 - **Scope Assessment**: analyze current code structure and identify refactoring targets
 - **Item Decomposition**: break refactoring goals into well-ordered, behavior-preserving items
 
-Always produce a validated `refactor-list.json` that conforms to `dev-pipeline-refactor-list-v1`.
+Always produce a validated `.prizmkit/plans/refactor-list.json` that conforms to `dev-pipeline-refactor-list-v1`.
 
 ## Invocation Commitment (Hard Rule)
 
@@ -31,24 +31,24 @@ The user chose this skill intentionally. Respect that choice.
 - Create, modify, or delete source code files (*.js, *.ts, *.py, *.go, *.html, *.css, etc.)
 - Execute refactoring operations (rename, move, extract, etc.)
 - Run build/install/test commands
-- Execute any implementation action beyond writing `refactor-list.json`
+- Execute any implementation action beyond writing `.prizmkit/plans/refactor-list.json`
 
 **Your ONLY writable outputs are:**
-1. `refactor-list.json` (project root)
-2. Draft backups in `.prizmkit/planning/`
+1. `.prizmkit/plans/refactor-list.json` (`.prizmkit/plans/`)
+2. Draft backups in `.prizmkit/plans/` (e.g., `refactor-list.draft.json`)
 
 **After planning is complete**, you MUST:
 1. Present the summary and recommended next step
 2. **Ask the user explicitly** whether they want to proceed to execution
-3. If the user agrees -> recommend invoking `refactor-pipeline-launcher` or running `run-refactor.sh` (do NOT execute it yourself)
-4. If the user wants to adjust -> continue refining `refactor-list.json`
+3. If the user agrees → recommend invoking `refactor-pipeline-launcher` (do NOT execute it yourself)
+4. If the user wants to adjust → continue refining `.prizmkit/plans/refactor-list.json`
 5. **NEVER auto-execute** the pipeline, launcher, or any implementation step
 
 ## When to Use
 
 Trigger this skill for requests like:
 - "Plan refactoring", "Scope a restructuring"
-- "Prepare refactor-list.json", "Prepare dev-pipeline input for refactoring"
+- "Prepare .prizmkit/plans/refactor-list.json", "Prepare dev-pipeline input for refactoring"
 - "Assess code for refactoring", "Identify refactoring targets"
 - "Plan a code migration", "Decompose a large refactor"
 
@@ -86,7 +86,7 @@ Before questions, check optional context files (never block if absent):
 - `.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 `refactor-list.json` (if appending additional items)
+- 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:
   ```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'
@@ -106,13 +106,13 @@ Full Q&A -> code analysis -> item generation. Used when starting from scratch or
 When an existing analysis report (e.g., `refactor-analysis.md`) is available, skip the analysis phase and proceed directly to item decomposition.
 
 ### Mode C: Validate
-Validate an existing `refactor-list.json` without regenerating it:
+Validate an existing `.prizmkit/plans/refactor-list.json` without regenerating it:
 ```bash
-python3 ${SKILL_DIR}/scripts/validate-and-generate-refactor.py validate --input refactor-list.json
+python3 ${SKILL_DIR}/scripts/validate-and-generate-refactor.py validate --input .prizmkit/plans/refactor-list.json
 ```
 
 ### Mode D: Summary
-Display a human-readable summary of an existing `refactor-list.json`:
+Display a human-readable summary of an existing `.prizmkit/plans/refactor-list.json`:
 - Item count, dependency graph, complexity distribution, behavior preservation strategies
 
 ## Interactive Mode — Core Workflow
@@ -240,12 +240,19 @@ Continue until all items are confirmed or skipped.
 
 ### Phase 6: Completeness Review
 
-**Goal**: Check the full item set for consistency and gaps.
+**Goal**: Check the full item set for consistency, gaps, and headless execution readiness.
 
 1. **Dependency ordering check**: Verify items form a valid DAG (no cycles). Items should be ordered: safe renames -> extract/inline -> structural changes -> migrations
 2. **Behavior preservation check**: Every item must have a declared preservation strategy. Flag any item with `manual` strategy and no test coverage.
 3. **Gap detection**: Are there intermediate steps needed between items? Does item A's output match item B's input assumption?
 4. **Cross-module impact**: Do any items affect modules outside the declared scope?
+5. **Headless Execution Readiness**: The refactor pipeline runs each item through an autonomous AI session with NO human interaction. For each item, verify:
+   - **Scope clarity**: Are all affected files explicitly listed? The AI must know exactly where to look.
+   - **Refactoring instructions**: Is the description specific enough to execute without ambiguity?
+     - ❌ "Clean up the utils module" — what exactly should change?
+     - ✅ "Extract validation functions (validateEmail, validatePhone, validateUrl) from src/utils/helpers.ts into src/utils/validation.ts. Update all 12 import sites. Preserve existing function signatures."
+   - **Behavior preservation**: Is it clear what tests to run and what behavior must be preserved?
+   - **Dependency context**: If item depends on earlier refactors, does the description reference what changed?
 
 Present review summary:
 ```
@@ -262,17 +269,17 @@ If issues found, discuss with user and resolve before proceeding.
 
 ### Phase 7: Generate & Validate
 
-**Goal**: Produce `refactor-list.json` and validate it.
+**Goal**: Produce `.prizmkit/plans/refactor-list.json` and validate it.
 
-1. Generate `refactor-list.json` at project root
+1. Generate `.prizmkit/plans/refactor-list.json` at `.prizmkit/plans/`
 2. Run validation:
    ```bash
-   python3 ${SKILL_DIR}/scripts/validate-and-generate-refactor.py validate --input refactor-list.json
+   python3 ${SKILL_DIR}/scripts/validate-and-generate-refactor.py validate --input .prizmkit/plans/refactor-list.json
    ```
 3. If validation fails -> fix issues and re-validate (max 3 attempts)
 4. If validation passes -> present final summary
 
-**CHECKPOINT CP-RP-6**: `refactor-list.json` generated and validated.
+**CHECKPOINT CP-RP-6**: `.prizmkit/plans/refactor-list.json` generated and validated.
 
 ## Checkpoints (Mandatory Gates)
 
@@ -284,18 +291,18 @@ If issues found, discuss with user and resolve before proceeding.
 | **CP-RP-3** | Items Decomposed | All items have deps, complexity, preservation strategy | 4 |
 | **CP-RP-4** | Items Confirmed | User confirmed/modified/skipped each item | 5 |
 | **CP-RP-5** | Completeness OK | DAG valid, preservation strategies declared, no gaps | 6 |
-| **CP-RP-6** | Output Valid | `refactor-list.json` passes validation script | 7 |
+| **CP-RP-6** | Output Valid | `.prizmkit/plans/refactor-list.json` passes validation script | 7 |
 
-**Resume Detection**: If existing artifacts found (partial `refactor-list.json`, draft in `.prizmkit/planning/`), offer to resume from the appropriate checkpoint.
+**Resume Detection**: If existing artifacts found (partial `.prizmkit/plans/refactor-list.json`, draft `refactor-list.draft.json` in `.prizmkit/plans/`), offer to resume from the appropriate checkpoint.
 
 ## Output Rules
 
-`refactor-list.json` must satisfy:
+`.prizmkit/plans/refactor-list.json` must satisfy:
 - `$schema` = `dev-pipeline-refactor-list-v1`
 - Non-empty `refactors` array
 - Sequential IDs: `R-001`, `R-002`, ...
 - Valid dependency DAG (no cycles)
-- Each item has a declared `behavior_preservation` strategy: `test-gate`, `snapshot`, or `manual`
+- 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.
 - `priority` must be a string: `"critical"`, `"high"`, `"medium"`, or `"low"`
 - New items default `status: "pending"`
 - English titles for stable slug generation
@@ -304,27 +311,16 @@ If issues found, discuss with user and resolve before proceeding.
 - `model` field is optional — omitting it means the pipeline uses $MODEL env or CLI default
 - `scope` object with nested structure: `files` array (target file paths) and `modules` array (module names)
 
-## Adversarial Critic Review
+## Adversarial Critic Defaults
 
-All refactoring items support optional critic review for additional quality assurance. The critic mechanism helps validate that refactoring preserves behavior while improving code quality.
+Set default critic fields for each refactor item. The user can override per-item.
 
-### Default Critic Behavior
-
-| Priority | Complexity | `critic` | `critic_count` | Rationale |
-|----------|-----------|----------|----------------|-----------|
-| critical | high | `true` | `3` | Multi-critic voting for high-risk refactors |
-| critical | medium/low | `true` | `1` | Single critic for critical-priority refactors |
-| high | high | `true` | `1` | Single critic for high-complexity refactors |
-| high | medium/low | `false` | (omitted) | Skip critic for simpler high-priority items |
-| medium | any | `false` | (omitted) | Skip critic for medium-priority refactors |
-| low | any | `false` | (omitted) | Skip critic for low-priority refactors |
-
-- `critic: true` — Enable adversarial review after refactoring completion
-- `critic_count: 1` — Single critic agent reviews the refactor
-- `critic_count: 3` — Three critic agents vote on the refactor quality
-- Critic verifies: behavior preservation strategy followed, code quality improved, no regressions, tests passing
-
-**User Override**: During planning phases, users can opt to enable/disable critic on a per-item basis.
+| Priority | Complexity | `critic` | `critic_count` |
+|----------|-----------|----------|----------------|
+| critical | high | `true` | `3` |
+| critical | medium/low | `true` | `1` |
+| high | high | `true` | `1` |
+| other combinations | any | `false` | (omitted) |
 
 ---
 
@@ -423,21 +419,7 @@ Take the highest of these individual assessments as the item's complexity.
 
 ## Next-Step Execution Policy (after planning)
 
-Recommend these three options in this strict order:
-
-1. **Preferred**: invoke `refactor-pipeline-launcher` skill (natural-language handoff)
-2. **Fallback A**: run daemon wrapper
-   ```bash
-   ./dev-pipeline/launch-refactor-daemon.sh start refactor-list.json
-   ./dev-pipeline/launch-refactor-daemon.sh status
-   ```
-3. **Fallback B**: run direct foreground script
-   ```bash
-   ./dev-pipeline/run-refactor.sh run
-   ./dev-pipeline/run-refactor.sh status
-   ```
-
-When launcher is available, do not prioritize raw scripts.
+Recommend invoking `refactor-pipeline-launcher` to configure and launch the dev-pipeline. Do NOT recommend running shell scripts directly — that is the launcher's responsibility.
 
 ## Error Recovery & Resume
 
@@ -445,16 +427,16 @@ Key behaviors:
 - Warnings only -> proceed with user approval
 - Critical errors -> group by type, auto-fix where possible, max 3 total attempts
 - Interrupted session -> detect checkpoint from existing artifacts, offer resume or restart
-- `refactor-list.json` MUST be written to project root (same level as `package.json` / `.git`)
+- `.prizmkit/plans/refactor-list.json` MUST be written to `.prizmkit/plans/` (project root level: `./{root}/.prizmkit/plans/refactor-list.json`)
 
 ### Resume Detection
 
 | Artifact Found | Resume From |
 |---------------|------------|
 | Nothing | Phase 1: Project Context |
-| Draft in `.prizmkit/planning/` | Phase matching draft state |
-| Partial `refactor-list.json` | Phase 6: Completeness Review |
-| Valid `refactor-list.json` | Mode D: Summary |
+| Draft in `.prizmkit/plans/` | Phase matching draft state |
+| Partial `.prizmkit/plans/refactor-list.json` | Phase 6: Completeness Review |
+| Valid `.prizmkit/plans/refactor-list.json` | Mode D: Summary |
 
 ## Session Exit Gate
 
@@ -464,11 +446,11 @@ Prevent accidental session exit without deliverable completion.
 Activate exit gate when ALL are true:
 - User invoked `/refactor-planner` (not just mentioned refactoring)
 - Current phase < Phase 7 (validation not yet passed)
-- No valid `refactor-list.json` has been written in this session
+- No valid `.prizmkit/plans/refactor-list.json` has been written in this session
 
 ### Gate Behavior
 When the session appears to be ending:
-1. **Remind**: "You set out to produce `refactor-list.json` but we haven't completed it yet."
+1. **Remind**: "You set out to produce `.prizmkit/plans/refactor-list.json` but we haven't completed it yet."
 2. **Offer 3 options**:
    - **(a) Continue to completion** — resume from current phase
    - **(b) Save draft & exit** — write current progress as draft, exit session

package/bundled/skills/refactor-planner/scripts/validate-and-generate-refactor.py

@@ -4,14 +4,14 @@ validate-and-generate-refactor.py - Validate and generate refactor-list.json fil
 for the dev-pipeline system.
 
 Commands:
-  validate    Validate an existing refactor-list.json
-  template    Generate a blank template refactor-list.json
-  summary     Print a summary table of refactors from a refactor-list.json
+  validate    Validate an existing .prizmkit/plans/refactor-list.json
+  template    Generate a blank template .prizmkit/plans/refactor-list.json
+  summary     Print a summary table of refactors from a .prizmkit/plans/refactor-list.json
 
 Usage:
-  python3 validate-and-generate-refactor.py validate --input refactor-list.json [--output validated.json]
-  python3 validate-and-generate-refactor.py template --output refactor-list.json
-  python3 validate-and-generate-refactor.py summary --input refactor-list.json [--format markdown|json]
+  python3 validate-and-generate-refactor.py validate --input .prizmkit/plans/refactor-list.json [--output validated.json]
+  python3 validate-and-generate-refactor.py template --output .prizmkit/plans/refactor-list.json
+  python3 validate-and-generate-refactor.py summary --input .prizmkit/plans/refactor-list.json [--format markdown|json]
 
 Python 3.6+ required. No external dependencies.
 """
@@ -712,15 +712,15 @@ def cmd_summary(args):
 
 def main():
     parser = argparse.ArgumentParser(
-        description="Validate and generate refactor-list.json files for the dev-pipeline system.",
+        description="Validate and generate .prizmkit/plans/refactor-list.json files for the dev-pipeline system.",
         formatter_class=argparse.RawDescriptionHelpFormatter,
         epilog=(
             "Examples:\n"
-            "  %(prog)s validate --input refactor-list.json\n"
-            "  %(prog)s validate --input refactor-list.json --output validated.json\n"
-            "  %(prog)s template --output refactor-list.json\n"
-            "  %(prog)s summary --input refactor-list.json\n"
-            "  %(prog)s summary --input refactor-list.json --format json\n"
+            "  %(prog)s validate --input .prizmkit/plans/refactor-list.json\n"
+            "  %(prog)s validate --input .prizmkit/plans/refactor-list.json --output validated.json\n"
+            "  %(prog)s template --output .prizmkit/plans/refactor-list.json\n"
+            "  %(prog)s summary --input .prizmkit/plans/refactor-list.json\n"
+            "  %(prog)s summary --input .prizmkit/plans/refactor-list.json --format json\n"
         ),
     )
 
@@ -729,10 +729,10 @@ def main():
     # -- validate --
     p_validate = subparsers.add_parser(
         "validate",
-        help="Validate an existing refactor-list.json",
+        help="Validate an existing .prizmkit/plans/refactor-list.json",
     )
     p_validate.add_argument(
-        "--input", required=True, help="Path to input refactor-list.json"
+        "--input", required=True, help="Path to input .prizmkit/plans/refactor-list.json"
     )
     p_validate.add_argument(
         "--output", help="Path to write validated output (optional)"
@@ -741,7 +741,7 @@ def main():
     # -- template --
     p_template = subparsers.add_parser(
         "template",
-        help="Generate a blank template refactor-list.json",
+        help="Generate a blank template .prizmkit/plans/refactor-list.json",
     )
     p_template.add_argument(
         "--output", required=True, help="Path to write template file"
@@ -750,10 +750,10 @@ def main():
     # -- summary --
     p_summary = subparsers.add_parser(
         "summary",
-        help="Print a summary table of refactors from a refactor-list.json",
+        help="Print a summary table of refactors from a .prizmkit/plans/refactor-list.json",
     )
     p_summary.add_argument(
-        "--input", required=True, help="Path to input refactor-list.json"
+        "--input", required=True, help="Path to input .prizmkit/plans/refactor-list.json"
     )
     p_summary.add_argument(
         "--format",