prizmkit 1.1.6 → 1.1.8

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

@@ -19,7 +19,7 @@ User says:
 
 **Do NOT use this skill when:**
 - User only wants to plan refactoring (use `refactor-planner` directly)
-- User only wants to launch pipeline for existing refactor-list.json (use `refactor-pipeline-launcher`)
+- User only wants to launch pipeline for existing .prizmkit/plans/refactor-list.json (use `refactor-pipeline-launcher`)
 - User wants to add features (use `feature-workflow`)
 - User wants to fix bugs (use `bug-planner` + `bugfix-pipeline-launcher`)
 
@@ -32,7 +32,7 @@ refactor-workflow <target / goals>
    │
    ├── Phase 1: Brainstorm → interactive Q&A until refactoring goals are clear
    │
-   ├── Phase 2: Plan → refactor-planner → refactor-list.json
+   ├── Phase 2: Plan → refactor-planner → .prizmkit/plans/refactor-list.json
    │
    ├── Phase 3: Launch → refactor-pipeline-launcher → pipeline execution
    │
@@ -44,7 +44,7 @@ refactor-workflow <target / goals>
 | Phase | Action | Result |
 |-------|--------|--------|
 | 1 | **Brainstorm** — interactive Q&A with user | Fully clarified refactoring goals |
-| 2 | Call `refactor-planner` with clarified goals | `refactor-list.json` with N refactor items |
+| 2 | Call `refactor-planner` with clarified goals | `.prizmkit/plans/refactor-list.json` with N refactor items |
 | 3 | Call `refactor-pipeline-launcher` | Pipeline started (execution mode chosen by user via launcher) |
 | 4 | Monitor progress | Status updates, completion report |
 
@@ -52,7 +52,7 @@ refactor-workflow <target / goals>
 
 Without this skill, users must:
 1. Figure out all refactoring goals and scope themselves
-2. Invoke `refactor-planner` → wait for refactor-list.json
+2. Invoke `refactor-planner` → wait for .prizmkit/plans/refactor-list.json
 3. Invoke `refactor-pipeline-launcher` → wait for pipeline start
 4. Manually check progress
 
@@ -81,18 +81,18 @@ Natural language description of the refactoring goals. Can be:
 
 Flow: brainstorm → refactor-planner → refactor-pipeline-launcher → monitor
 
-**Mode B: From existing refactor-list.json**
+**Mode B: From existing .prizmkit/plans/refactor-list.json**
 
-When user says "run pipeline from existing file" or refactor-list.json already exists:
+When user says "run pipeline from existing file" or .prizmkit/plans/refactor-list.json already exists:
 - Skip brainstorm and `refactor-planner` (file already exists)
 - Invoke `refactor-pipeline-launcher` directly
 - Monitor and report progress
 
 **Mode C: Incremental (add to existing refactor plan)**
 
-When user says "add more refactors" or the project already has a refactor-list.json:
+When user says "add more refactors" or the project already has a .prizmkit/plans/refactor-list.json:
 - Brainstorm new refactoring goals with the user
-- Invoke `refactor-planner` in incremental mode (reads existing refactor-list.json)
+- Invoke `refactor-planner` in incremental mode (reads existing .prizmkit/plans/refactor-list.json)
 - Append new refactor items to existing list
 - Invoke `refactor-pipeline-launcher`
 - Monitor and report progress
@@ -227,7 +227,7 @@ Present this summary to the user and get explicit confirmation before proceeding
 
 ## Phase 2: Plan
 
-**Goal**: Generate structured refactor-list.json from the clarified refactoring goals.
+**Goal**: Generate structured .prizmkit/plans/refactor-list.json from the clarified refactoring goals.
 
 **STEPS**:
 
@@ -235,16 +235,18 @@ Present this summary to the user and get explicit confirmation before proceeding
    - Pass the structured goals summary as input — NOT the raw user conversation
    - For new refactoring: standard planning mode
    - For existing projects with `--incremental`: incremental planning mode
+   - **Input**: Markdown goals summary (refactor targets, scope, behavior preservation strategy)
+   - **Output**: `.prizmkit/plans/refactor-list.json` (schema: `dev-pipeline-refactor-list-v1`) containing `project_name`, `refactors[]` with id (R-NNN), title, description, scope, type, priority, complexity, behavior_preservation, acceptance_criteria, dependencies, status
 
 2. **Interactive planning** (if refactor-planner requires clarification):
    - Because Phase 1 was thorough, refactor-planner should need minimal clarification
    - If questions arise, answer from the Phase 1 context or pass through to user
 
 3. **Validate output**:
-   - Confirm `refactor-list.json` exists
+   - Confirm `.prizmkit/plans/refactor-list.json` exists
    - Show summary: total refactor items, complexity distribution, dependencies
 
-**CHECKPOINT CP-RW-1**: `refactor-list.json` generated and validated.
+**CHECKPOINT CP-RW-1**: `.prizmkit/plans/refactor-list.json` generated and validated.
 
 **If user says `--from <file>`**: Skip Phase 1 and Phase 2 entirely.
 
@@ -267,9 +269,11 @@ Present this summary to the user and get explicit confirmation before proceeding
    ```
 
 2. **Invoke `refactor-pipeline-launcher` skill**:
+   - **Input**: Path to validated `.prizmkit/plans/refactor-list.json`
    - The launcher handles all prerequisites checks
    - The launcher presents execution mode choices to the user (foreground/background/manual)
    - Do NOT duplicate execution mode selection here — let the launcher handle it
+   - **Output**: PID/status, log file path, execution mode selected
    - Returns PID/status and log file location
 
 3. **Verify launch success**:
@@ -299,8 +303,8 @@ Present this summary to the user and get explicit confirmation before proceeding
 3. **Periodic progress reports** (when user asks):
    ```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
    ```
 
@@ -329,12 +333,12 @@ The workflow supports resuming by detecting existing state:
 
 | State Found | Resume From |
 |-------------|------------|
-| No `refactor-list.json` | Phase 1: Brainstorm |
-| `refactor-list.json` exists, no pipeline state | Phase 3: Launch |
-| `refactor-list.json` + pipeline state exists | Phase 4: Monitor (check status) |
+| No `.prizmkit/plans/refactor-list.json` | Phase 1: Brainstorm |
+| `.prizmkit/plans/refactor-list.json` exists, no pipeline state | Phase 3: Launch |
+| `.prizmkit/plans/refactor-list.json` + pipeline state exists | Phase 4: Monitor (check status) |
 | All refactors completed | Report completion, suggest next steps |
 
-**Resume**: If `refactor-list.json` exists, ask user: "Existing refactor plan found with N items. Resume pipeline or re-plan?"
+**Resume**: If `.prizmkit/plans/refactor-list.json` exists, ask user: "Existing refactor plan found with N items. Resume pipeline or re-plan?"
 
 ---
 
@@ -359,7 +363,7 @@ While the pipeline runs, the user can continue the conversation:
 | Brainstorming stalls | Offer concrete options: "Would you prefer incremental or comprehensive refactoring?" |
 | No tests exist for target module | WARN user, recommend writing tests first before refactoring |
 | `refactor-planner` cannot parse goals | Refine the goals summary and retry |
-| `refactor-list.json` generation failed | Show error, retry with refined input |
+| `.prizmkit/plans/refactor-list.json` generation failed | Show error, retry with refined input |
 | Pipeline launch failed | Show daemon log, suggest manual start |
 | All refactor items blocked/failed | Show status, suggest retrying specific items |
 | User wants to cancel mid-brainstorming | Save conversation context, offer to resume later |
@@ -371,7 +375,7 @@ While the pipeline runs, the user can continue the conversation:
 
 | Skill | Relationship |
 |-------|-------------|
-| `refactor-planner` | **Called by Phase 2** — generates refactor-list.json from clarified goals |
+| `refactor-planner` | **Called by Phase 2** — generates .prizmkit/plans/refactor-list.json from clarified goals |
 | `refactor-pipeline-launcher` | **Called by Phase 3** — starts pipeline (handles execution mode selection) |
 | `feature-workflow` | **Alternative** — for new feature development |
 | `bug-fix-workflow` | **Alternative** — for bug fix workflows |
@@ -397,7 +401,7 @@ While the pipeline runs, the user can continue the conversation:
 ## Output
 
 - Structured refactoring goals summary (Phase 1 artifact)
-- `refactor-list.json` (Phase 2 artifact)
+- `.prizmkit/plans/refactor-list.json` (Phase 2 artifact)
 - Pipeline execution (Phase 3)
 - Progress updates (Phase 4)
 - Multiple git commits with `refactor(<scope>):` prefix

package/package.json

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

package/src/clean.js

@@ -119,10 +119,10 @@ export async function runClean(directory, options = {}) {
     '.prizm-docs',        // AI-generated project context docs
     'CODEBUDDY.md',
     'CLAUDE.md',
-    'feature-list.json',          // feature-planner output
-    'bug-fix-list.json',          // bug-planner output
-    'project-brief.md',           // feature-planner project brief
-    'project-conventions.json',   // feature-planner coding conventions
+    path.join('.prizmkit', 'plans', 'feature-list.json'),          // feature-planner output
+    path.join('.prizmkit', 'plans', 'bug-fix-list.json'),          // bug-planner output
+    path.join('.prizmkit', 'plans', 'project-brief.md'),           // feature-planner project brief
+    path.join('.prizmkit', 'project-conventions.json'),   // feature-planner coding conventions
     path.join('.codebuddy', 'settings.json'),
     path.join('.claude', 'settings.json'),
     path.join('.claude', 'team-info.json'),

package/src/gitignore-template.js

@@ -14,8 +14,8 @@ export function generateGitignore(options = {}) {
     '# PrizmKit Runtime Artifacts',
     '# ===========================',
     '',
-    '# PrizmKit 运行时配置与产物',
-    '.prizmkit/',
+    '# PrizmKit 运行时状态（不提交）',
+    '.prizmkit/state/',
     '',
     '# 多 Agent 协作临时工作区',
     '.dev-team/',
@@ -24,18 +24,17 @@ export function generateGitignore(options = {}) {
     '# .prizm-docs/',
     '',
     '# 规划产物（按需决定是否提交）',
-    '# feature-list.json',
-    '# bug-fix-list.json',
-    '# project-brief.md',
+    '# .prizmkit/plans/',
     '# project-conventions.json',
     '',
   ];
 
   if (options.pipeline) {
     lines.push(
-      '# Dev-Pipeline 运行时状态',
-      'dev-pipeline/state/',
-      'dev-pipeline/bugfix-state/',
+      '# Dev-Pipeline 运行时状态（已迁移到 .prizmkit/state/）',
+      '.prizmkit/state/features/',
+      '.prizmkit/state/bugfix/',
+      '.prizmkit/state/refactor/',
       'dev-pipeline/logs/',
       'dev-pipeline/*.pid',
       '',

package/src/scaffold.js

@@ -647,8 +647,10 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
     return [];
   }
 
-  await fs.ensureDir(path.join(pipelineTarget, 'state'));
-  await fs.ensureDir(path.join(pipelineTarget, 'bugfix-state'));
+  await fs.ensureDir(path.join(projectRoot, '.prizmkit', 'plans'));
+  await fs.ensureDir(path.join(projectRoot, '.prizmkit', 'state', 'features'));
+  await fs.ensureDir(path.join(projectRoot, '.prizmkit', 'state', 'bugfix'));
+  await fs.ensureDir(path.join(projectRoot, '.prizmkit', 'state', 'refactor'));
 
   // 动态扫描 bundled dev-pipeline 目录，排除不应安装到用户项目的内容
   const EXCLUDE = new Set(['tests', 'docs', '__pycache__', 'node_modules', '.DS_Store']);