prizmkit 1.1.94 → 1.1.96

package/bundled/skills/prizmkit-deploy/references/firewall-setup.md

@@ -5,17 +5,17 @@ Read this file when the user wants AI-assisted firewall configuration during boo
 ## Flow
 
 1. After core tools are installed, ask the user:
-   > "是否需要帮你配置防火墙（ufw）？只开放必要的端口，提高服务器安全性。"
+   > "Want me to configure the firewall (ufw)? Only necessary ports will be opened, improving server security."
 
 2. If user declines: skip, record to deploy config.
 
 3. If user agrees, ask which additional ports to open (beyond SSH/HTTP/HTTPS):
-   > "默认只开放 SSH(22)、HTTP(80)、HTTPS(443)。蓝绿部署预览端口（3101/3102）要不要也开放？如果需要其他端口（如数据库远程管理），可以一起列出来。"
+   > "By default only SSH(22), HTTP(80), HTTPS(443) are opened. Should the blue/green preview ports (3101/3102) also be opened? If you need other ports (e.g., for remote database management), list them together."
 
 4. Collect ports, then ask:
-   > "防火墙规则已整理好。是我直接上去改，还是你自己来？"
-   > - **A. 你帮我改** — AI 执行 ufw 命令
-   > - **B. 我自己改** — 输出规则清单，用户手工执行
+   > "Firewall rules are ready. Should I apply them directly, or will you do it yourself?"
+   > - **A. You apply them** — AI runs ufw commands
+   > - **B. I'll do it myself** — output rule list, user executes manually
 
 ## Planned rules (output before executing)
 

package/bundled/skills/prizmkit-deploy/references/ssh-execution-flow.md

@@ -4,7 +4,7 @@ Pipeline runs in strict order. Each group must complete before the next begins.
 
 ## Pre-flight — Change Summary
 
-Show what will be deployed using `git log --oneline <last-deployed-commit>..HEAD`. If first deployment, show last 5 commits. If no new commits, warn "没有新的代码变更。确定要重新部署吗？"
+Show what will be deployed using `git log --oneline <last-deployed-commit>..HEAD`. If first deployment, show last 5 commits. If no new commits, warn "No new code changes. Are you sure you want to redeploy?"
 
 ## Group 1 — Pre-flight & Prepare
 

package/bundled/skills/prizmkit-deploy/references/ssl-setup.md

@@ -15,11 +15,11 @@ Also check `/etc/hostname` for vendor patterns.
 ## Step 2 — Choose SSL strategy
 
 - **Cloud vendor detected** → ask user:
-  > "检测到服务器运行在 <云厂商>。用哪种 SSL 方案？"
-  > - **A. Let's Encrypt 免费证书（推荐）** — 一行命令永久自动续期，最省心
-  > - **B. <云厂商> 自有证书** — 需手动下载配置，1年有效期需手动续期
+  > "Detected the server is running on <cloud-vendor>. Which SSL approach?"
+  > - **A. Let's Encrypt free certificate (recommended)** — one command for permanent auto-renewal, hassle-free
+  > - **B. <cloud-vendor> native certificate** — manual download/config, 1-year validity requires manual renewal
   >
-  > 选 A 我直接帮你搞定；选 B 你需要在云控制台下载证书后告诉我路径。
+  > Choose A and I'll set it up for you; choose B and you'll need to download the certificate from the cloud console and tell me the path.
 - **No cloud vendor / unknown** → use certbot directly, no choice needed.
 
 ## Step 3 — Certbot install & certificate request

package/bundled/skills/prizmkit-prizm-docs/assets/prizm-docs-format.md

@@ -544,7 +544,7 @@ JSON:
   "hooks": {
     "UserPromptSubmit": [
       {
-        "matcher": "(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b|提交|推送|收尾|完成任务|合并|发版|发布",
+        "matcher": "(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b",
         "hooks": [
           {
             "type": "command",

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

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-test"
-description: "Full-stack test generation and orchestration. Detects architecture, discovers/runs existing tests, analyzes coverage gaps, generates missing unit/integration/E2E tests including business-specific boundary cases, validates every interface with a required boundary coverage matrix, and outputs a unified report. Use after completing development to verify quality before deploy. Trigger on: 'test', 'run tests', 'check quality', 'verify code', 'generate tests', 'test coverage', 'fill test gaps', 'boundary tests', 'edge cases', 'quality check', '测试', '验证', '跑测试', '补测试', '边界测试'. (project)"
+description: "Full-stack test generation and orchestration. Detects architecture, discovers/runs existing tests, analyzes coverage gaps, generates missing unit/integration/E2E tests including business-specific boundary cases, validates every interface with a required boundary coverage matrix, and outputs a unified report. Use after completing development to verify quality before deploy. Trigger on: 'test', 'run tests', 'check quality', 'verify code', 'generate tests', 'test coverage', 'fill test gaps', 'boundary tests', 'edge cases', 'quality check', 'add tests'. (project)"
 ---
 
 # PrizmKit Test
@@ -11,7 +11,7 @@ A comprehensive test generation and orchestration skill. Discovers existing test
 - After completing one or more features/refactors/bugfixes
 - As a quality gate before deploy
 - Project has a test framework installed but zero tests written (first-time test generation)
-- User says "test", "run tests", "verify", "check quality", "补测试"
+- User says "test", "run tests", "verify", "check quality", "add tests"
 
 ### When NOT to Use
 - Project has no test framework AND no code to test

package/bundled/skills/recovery-workflow/evals/evals.json

@@ -5,7 +5,7 @@
     {
       "id": 1,
       "name": "bugfix-mid-fix",
-      "prompt": "session 断了，帮我恢复一下",
+      "prompt": "My session broke, help me recover",
       "expected_output": "Should auto-detect bug-fix-workflow from fix/B-001-* branch. Should detect fix-plan.md + code changes → infer Phase 5 (Review). Should display recovery report with workflow type, phase, artifacts, code stats. After user confirms, should invoke /prizmkit-code-review on existing changes.",
       "setup_description": "Create fix/B-001-login-crash branch, .prizmkit/bugfix/B-001/fix-plan.md, modify 3 source files + 1 test file. No fix-report.md, no commits ahead of main.",
       "files": []
@@ -13,7 +13,7 @@
     {
       "id": 2,
       "name": "bugfix-plan-only",
-      "prompt": "继续之前的工作",
+      "prompt": "Continue the previous work",
       "expected_output": "Should auto-detect bug-fix-workflow from fix/B-002-* branch. Should detect fix-plan.md but no code changes → infer Phase 4 (Fix). Should read fix-plan.md and start implementing the fix.",
       "setup_description": "Create fix/B-002-null-pointer branch, .prizmkit/bugfix/B-002/fix-plan.md with diagnosis and fix approach. No code changes.",
       "files": []
@@ -37,7 +37,7 @@
     {
       "id": 5,
       "name": "no-workflow-detected",
-      "prompt": "恢复",
+      "prompt": "recover",
       "expected_output": "Should detect no workflow signatures in workspace. Should display guidance message suggesting /feature-workflow, /bug-fix-workflow, or /refactor-workflow. Should NOT attempt any recovery actions.",
       "setup_description": "Clean workspace on main branch. No .prizmkit/plans/feature-list.json, no bug-fix artifacts, no .prizmkit/plans/refactor-list.json, no fix/* or feat/* or refactor/* branches.",
       "files": []

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

@@ -239,9 +239,8 @@ Before generating `.prizmkit/plans/bug-fix-list.json`, perform a holistic scan a
 
 **Step 4 — Present review table**: Display the completeness assessment using the template in `${SKILL_DIR}/assets/bug-confirmation-template.md` (§Completeness Review Template).
 
-For any items that need attention, ask targeted questions to fill gaps. Iterate until the user confirms all bugs are adequately described. Present bilingual prompt:
+For any items that need attention, ask targeted questions to fill gaps. Iterate until the user confirms all bugs are adequately described. Present the prompt:
 
-> "以上是完整性审查结果。需要补充的项目是否逐一补充？还是先跳过，之后再完善？"
 > "Above is the completeness review. Items needing more detail — address them now, or proceed and refine later?"
 
 Only proceed to Phase 5 after user confirms.

package/bundled/skills-windows/bug-planner/assets/bug-confirmation-template.md

@@ -23,9 +23,9 @@ Present this after extracting and clarifying each bug:
 ```
 
 Then ask three confirmation questions:
-1. "描述是否准确？是否需要修改？" / "Is the description accurate? Any corrections?"
-2. "是否需要补充更多细节？（复现步骤、环境信息、相关代码位置等）" / "Need to add more details? (reproduction steps, environment, related code locations, etc.)"
-3. "验证条件是否具体到 pipeline 可以自主判断修复成功？" / "Are the acceptance criteria specific enough that the pipeline can autonomously verify the fix?"
+1. "Is the description accurate? Any corrections?"
+2. "Need to add more details? (reproduction steps, environment, related code locations, etc.)"
+3. "Are the acceptance criteria specific enough that the pipeline can autonomously verify the fix?"
 
 Only finalize the bug entry after user confirms all three points.
 

package/bundled/skills-windows/feature-planner/SKILL.md

@@ -285,7 +285,7 @@ For simple incremental planning, skip detailed Phase 2-3 analysis:
 4. Draft features (title + description + acceptance_criteria + dependencies)
 5. Write draft to `.prizmkit/plans/feature-list.draft.json`, then call the generate script:
    ```powershell
-   Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --mode incremental
+   Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
    ```
 6. If valid → summarize and recommend next step
 7. If invalid → apply fixes to the draft, re-run generate (max 2 attempts, then escalate to full workflow)
@@ -336,7 +336,7 @@ Key requirements:
 1. Write a draft JSON to a temporary path (e.g., `.prizmkit/plans/feature-list.draft.json`)
 2. Call the generate script to validate and produce the final file:
 ```powershell
-Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json --mode <new|incremental>
+Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py generate --input .prizmkit/plans/feature-list.draft.json --output .prizmkit/plans/feature-list.json
 ```
 The script fills in defaults (`$schema`, `created_at`, `created_by`), validates all fields, and writes the final file only if validation passes. If validation fails, fix the draft and retry.
 

package/bundled/skills-windows/feature-planner/references/error-recovery.md

@@ -4,7 +4,7 @@ Structured error handling for validation failures, interrupted sessions, and che
 
 ## Validation Failures
 
-When `Invoke-PrizmPython scripts/validate-and-generate.py validate --input <file> --mode <mode>` returns errors:
+When `Invoke-PrizmPython scripts/validate-and-generate.py validate --input <file>` returns errors:
 
 ### Parse validation output
 Script returns JSON with `"valid": false`, `"errors": [...]`, `"warnings": [...]`

package/bundled/skills-windows/feature-planner/references/incremental-feature-planning.md

@@ -83,7 +83,7 @@ Keep dependency correctness as first constraint.
 ### Step 5: Validate
 Run after defining `Invoke-PrizmPython` from the main `SKILL.md`:
 ```powershell
-Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py validate --input feature-list.json --mode incremental
+Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py validate --input feature-list.json
 ```
 
 Fix and re-run until pass.

package/bundled/skills-windows/feature-planner/references/new-project-planning.md

@@ -55,7 +55,7 @@ Split into `sub_features` when:
 1. Write `feature-list.json`.
 2. Run the command below after defining `Invoke-PrizmPython` from the main `SKILL.md`:
    ```powershell
-   Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py validate --input feature-list.json --mode new
+   Invoke-PrizmPython ${SKILL_DIR}/scripts/validate-and-generate.py validate --input feature-list.json
    ```
 3. Fix all errors, then re-run.
 

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

@@ -11,12 +11,16 @@ Commands:
   grade       Generate grading results from eval runs (for npm run skill:review)
 
 Usage:
-  python3 validate-and-generate.py validate --input .prizmkit/plans/feature-list.json [--output validated.json] [--mode new|incremental]
+  python3 validate-and-generate.py validate --input .prizmkit/plans/feature-list.json [--output validated.json]
   python3 validate-and-generate.py template --output .prizmkit/plans/feature-list.json
-  python3 validate-and-generate.py generate --input draft.json --output .prizmkit/plans/feature-list.json [--mode new|incremental]
+  python3 validate-and-generate.py generate --input draft.json --output .prizmkit/plans/feature-list.json
   python3 validate-and-generate.py summary --input .prizmkit/plans/feature-list.json [--format markdown|json]
   python3 validate-and-generate.py grade --workspace /.codebuddy/skill-evals/feature-planner-workspace --iteration iteration-1
 
+Mode is determined automatically by --output path:
+  - Output file does NOT exist -> new plan (all features must be "pending")
+  - Output file already exists -> incremental append (existing features keep their status)
+
 Python 3.6+ required. No external dependencies.
 """
 
@@ -38,8 +42,6 @@ VALID_STATUSES = {"pending", "in_progress", "completed", "failed", "skipped", "s
 VALID_COMPLEXITIES = {"low", "medium", "high", "critical"}
 VALID_PRIORITIES = {"critical", "high", "medium", "low"}
 VALID_GRANULARITIES = {"feature", "sub_feature", "auto"}
-VALID_PLANNING_MODES = {"new", "incremental"}
-
 FEATURE_ID_RE = re.compile(r"^F-\d{3}(-[A-Z])?$")
 SUB_FEATURE_ID_RE = re.compile(r"^F-\d{3}-[A-Z]$")
 
@@ -156,13 +158,11 @@ def _detect_cycles(features):
 # ---------------------------------------------------------------------------
 
 
-def validate_feature_list(data, planning_mode="new"):
+def validate_feature_list(data, is_new_plan=True):
     """Validate a parsed feature-list data structure.
 
     Returns a dict with keys ``valid``, ``errors``, ``warnings``, ``stats``.
     """
-    if planning_mode not in VALID_PLANNING_MODES:
-        planning_mode = "new"
 
     errors = []
     warnings = []
@@ -299,7 +299,7 @@ def validate_feature_list(data, planning_mode="new"):
                     label, status, ", ".join(sorted(VALID_STATUSES))
                 )
             )
-        if planning_mode == "new" and status and status != "pending":
+        if is_new_plan and status and status != "pending":
             warnings.append(
                 "{}: status is '{}' (expected 'pending' for new plans)".format(label, status)
             )
@@ -680,7 +680,9 @@ def cmd_validate(args):
         print(json.dumps(result, indent=2, ensure_ascii=False))
         return 2
 
-    result = validate_feature_list(data, planning_mode=args.mode)
+    # Validate input file exists -> incremental mode (existing features keep their status)
+    is_new_plan = False
+    result = validate_feature_list(data, is_new_plan=is_new_plan)
 
     # Print results to stdout
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -758,9 +760,11 @@ def cmd_generate(args):
     for feature in data.get("features", []):
         feature.setdefault("status", "pending")
 
-    # Validate
-    mode = getattr(args, "mode", "new") or "new"
-    result = validate_feature_list(data, planning_mode=mode)
+    # Validate. Mode is determined by whether --output file already exists:
+    #   - does NOT exist -> new plan (all features must be "pending")
+    #   - already exists -> incremental append (existing features keep their status)
+    is_new_plan = not os.path.exists(args.output)
+    result = validate_feature_list(data, is_new_plan=is_new_plan)
 
     # Output validation result
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -856,7 +860,7 @@ def cmd_grade(args):
             continue
         
         # Run validation
-        result = validate_feature_list(data, planning_mode="new")
+        result = validate_feature_list(data, is_new_plan=True)
         
         # Create grading entry
         grade_entry = {
@@ -916,7 +920,6 @@ def main():
         epilog=(
             "Examples:\n"
             "  %(prog)s validate --input .prizmkit/plans/feature-list.json\n"
-            "  %(prog)s validate --input .prizmkit/plans/feature-list.json --mode incremental\n"
             "  %(prog)s validate --input .prizmkit/plans/feature-list.json --output validated.json\n"
             "  %(prog)s template --output .prizmkit/plans/feature-list.json\n"
             "  %(prog)s generate --input draft.json --output .prizmkit/plans/feature-list.json\n"
@@ -938,12 +941,6 @@ def main():
     p_validate.add_argument(
         "--output", help="Path to write validated output (optional)"
     )
-    p_validate.add_argument(
-        "--mode",
-        choices=["new", "incremental"],
-        default="new",
-        help="Validation mode (default: new)",
-    )
 
     # -- template --
     p_template = subparsers.add_parser(
@@ -965,12 +962,6 @@ def main():
     p_generate.add_argument(
         "--output", required=True, help="Path to write final feature-list.json"
     )
-    p_generate.add_argument(
-        "--mode",
-        choices=["new", "incremental"],
-        default="new",
-        help="Validation mode (default: new)",
-    )
 
     # -- summary --
     p_summary = subparsers.add_parser(

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

@@ -72,7 +72,7 @@ All three follow the same per-task flow. Detailed documentation policies (when t
 | `/prizmkit-code-review` | Diagnose issues + produce Fix Instructions | "review", "check code", "is it ready to commit" |
 | `/prizmkit-retrospective` | Sync .prizmkit/prizm-docs/ with code changes | "retrospective", "retro", "sync docs", "wrap up" |
 | `/prizmkit-committer` | Safe git commit with Conventional Commits | "commit", "submit", "finish", "ship it" |
-| `/prizmkit-test` | Generate + run tests, analyze coverage gaps, unified quality report | "test", "run tests", "check quality", "verify code", "补测试" |
+| `/prizmkit-test` | Generate + run tests, analyze coverage gaps, unified quality report | "test", "run tests", "check quality", "verify code", "add tests" |
 | `/prizmkit-deploy` | Universal deployment gateway: SSH automation, cloud/Docker guided setup, status/logs/rollback | "deploy", "ship it", "go live", "rollback", "deploy status" |
 | `/prizmkit-init` | Project bootstrap + .prizmkit/prizm-docs/ setup | "init", "initialize", "take over this project" |
 | `/prizmkit-prizm-docs` | Doc management (init/status/rebuild/validate) | "check docs", "rebuild docs", "validate docs" |

package/bundled/skills-windows/prizmkit-deploy/SKILL.md

@@ -204,14 +204,14 @@ The following sections define the SSH deployment adapter — the only fully-auto
 After Discovery routes to SSH, **before** entering the configuration wizard, ask the user how they want to deploy.
 
 **First question:**
-> "你想怎么部署到服务器？"
-> - **A. 直接上传（快速上手）** — 本地构建，传到服务器启动。适合第一次部署。
-> - **B. CI/CD 自动部署（推荐）** — 配置 GitHub Actions，以后 `git push` 自动部署。
+> "How do you want to deploy to the server?"
+> - **A. Direct Upload (quick start)** — build locally, transfer to server and start. Good for first deployment.
+> - **B. CI/CD Auto-Deploy (recommended)** — configure GitHub Actions, then `git push` auto-deploys.
 
 **If user chooses CI/CD, second question:**
-> "CI/CD 有两种模式："
-> - **Push 模式** — GitHub Actions runner 编译，SCP 传到服务器。服务器压力小。
-> - **Pull 模式** — 服务器自己拉代码编译。配置更简单但需 Deploy Key。
+> "CI/CD has two modes:"
+> - **Push mode** — GitHub Actions runner builds, SCP transfers to server. Low server load.
+> - **Pull mode** — server pulls code and builds itself. Simpler config but requires a Deploy Key.
 
 For detailed mode descriptions and the full Push/Pull comparison table, read `references/deployment-modes.md`.
 
@@ -306,7 +306,7 @@ After generating the workflow, verify: the first `git push` to the configured br
 
 Before SSL, check if the user has a domain pointing to the server.
 
-1. Ask: "你有没有域名要绑定到这个项目？" If no domain → skip DNS + SSL, note in deploy.md.
+1. Ask: "Do you have a domain to bind to this project?" If no domain → skip DNS + SSL, note in deploy.md.
 2. Check DNS: `dig +short <domain> A`. If resolved → proceed to SSL.
 3. If not resolved: show the user DNS setup instructions. Full procedure in `references/dns-setup.md`.
 
@@ -360,7 +360,7 @@ If no previous release exists, rollback is not possible — state this clearly.
 
 After a successful direct-upload deployment, proactively offer CI/CD setup:
 
-> "部署成功。要不要顺手帮你配置 CI/CD 自动部署？以后 `git push` 就自动上线。"
+> "Deployment succeeded. Want me to set up CI/CD auto-deploy? After that, `git push` will auto-deploy."
 
 If user agrees, ask push vs pull, then configure accordingly. If Pull mode: set up deploy key. If Push mode: add GitHub Actions secrets. Generate `deploy.yml` from `references/ci-cd-workflows.md`, update `deployStrategy` in config, write upgrade event to history.
 

package/bundled/skills-windows/prizmkit-deploy/references/database-setup.md

@@ -6,9 +6,9 @@ Read this file when Discovery detected a database driver and the user wants AI-a
 
 During Discovery Step 1 (Project Detection), database drivers were already scanned. If a driver was detected, ask after bootstrap tools are installed:
 
-> "检测到项目使用了 <PostgreSQL/MySQL/Redis>，需要帮你在服务器上安装配置吗？"
-> - **需要** → 继续数据库安装
-> - **不需要** → 跳过，记录到 deploy.md，标注"数据库需用户自行配置"
+> "Detected the project uses <PostgreSQL/MySQL/Redis>. Want me to install and configure it on the server?"
+> - **Yes** → proceed with database installation
+> - **No** → skip, record in deploy.md with note "database must be configured by user"
 
 ## PostgreSQL setup
 
@@ -21,7 +21,7 @@ sudo -u postgres psql -c "GRANT ALL ON DATABASE <project> TO <project>;"
 
 - Generate a secure random password (32 chars, alphanumeric + symbols).
 - Write the connection string to `.prizmkit/deploy/secrets.local.json`: `DATABASE_URL=postgresql://<project>:<password>@localhost:5432/<project>`.
-- In deploy.md, write: "PostgreSQL 已安装，连接信息已记录到 `.prizmkit/deploy/secrets.local.json`（不提交到 git）".
+- In deploy.md, write: "PostgreSQL installed, connection info recorded in `.prizmkit/deploy/secrets.local.json` (not committed to git)".
 
 ## MySQL setup (future)
 

package/bundled/skills-windows/prizmkit-deploy/references/deployment-modes.md

@@ -34,14 +34,14 @@ Best for: simple setup, servers with sufficient CPU/RAM, projects where build is
 
 ## Comparison
 
-| 对比 | Push 模式 | Pull 模式 |
+| Aspect | Push mode | Pull mode |
 |------|----------|----------|
-| 构建位置 | GitHub Actions runner | 服务器本地 |
-| 服务器压力 | 低（只运行应用） | 高（编译+运行） |
-| 配置复杂度 | 中（需 SCP 传产物） | 低（只需 SSH 触发脚本） |
-| 适合场景 | 服务器配置低、编译重 | 部署简单优先、服务器性能充裕 |
-| Deploy Key 需要 | 不需要 | 需要 |
-| 产物传输 | SCP tarball | git pull（仅增量） |
+| Build location | GitHub Actions runner | Server (local) |
+| Server load | Low (runs app only) | High (build + run) |
+| Config complexity | Medium (needs SCP transfer) | Low (SSH-triggered script only) |
+| Best for | Low-spec servers, heavy builds | Simple setup, capable servers |
+| Deploy Key required | No | Yes |
+| Artifact transfer | SCP tarball | git pull (incremental) |
 
 ## Common ground between all modes
 

package/bundled/skills-windows/prizmkit-deploy/references/dns-setup.md

@@ -14,21 +14,21 @@ If not: continue below.
 ## Step 2 — DNS setup guidance
 
 ```
-域名 <example.com> 还未指向服务器 <服务器IP>。
+Domain <example.com> is not yet pointing to server <server-IP>.
 
-请在 DNS 服务商（如阿里云、Cloudflare、Namecheap）添加以下记录：
+Add the following record at your DNS provider (e.g., Alibaba Cloud, Cloudflare, Namecheap):
 
   Type:  A
   Name:  @
-  Value: <服务器IP>
+  Value: <server-IP>
   TTL:   600
 
-如果要同时支持 www 子域名：
+To also support the www subdomain:
   Type:  A
   Name:  www
-  Value: <服务器IP>
+  Value: <server-IP>
 
-配置完成后回复"好了"，我继续检查并配 SSL 证书。
+Reply "done" when configured, and I'll verify and set up the SSL certificate.
 ```
 
 ## Step 3 — Verify after user confirmation
@@ -39,4 +39,4 @@ If not: continue below.
 
 ## Edge case — IP-only deployment
 
-If user has no domain: skip DNS + SSL sections. Generate a note in deploy.md: "项目通过 IP 访问，未配置域名和 HTTPS。建议购买域名后运行 `/prizmkit-deploy setup-ssl`。"
+If user has no domain: skip DNS + SSL sections. Generate a note in deploy.md: "Project accessed via IP, no domain or HTTPS configured. Recommend purchasing a domain and running `/prizmkit-deploy setup-ssl`."

package/bundled/skills-windows/prizmkit-deploy/references/firewall-setup.md

@@ -5,17 +5,17 @@ Read this file when the user wants AI-assisted firewall configuration during boo
 ## Flow
 
 1. After core tools are installed, ask the user:
-   > "是否需要帮你配置防火墙（ufw）？只开放必要的端口，提高服务器安全性。"
+   > "Want me to configure the firewall (ufw)? Only necessary ports will be opened, improving server security."
 
 2. If user declines: skip, record to deploy config.
 
 3. If user agrees, ask which additional ports to open (beyond SSH/HTTP/HTTPS):
-   > "默认只开放 SSH(22)、HTTP(80)、HTTPS(443)。蓝绿部署预览端口（3101/3102）要不要也开放？如果需要其他端口（如数据库远程管理），可以一起列出来。"
+   > "By default only SSH(22), HTTP(80), HTTPS(443) are opened. Should the blue/green preview ports (3101/3102) also be opened? If you need other ports (e.g., for remote database management), list them together."
 
 4. Collect ports, then ask:
-   > "防火墙规则已整理好。是我直接上去改，还是你自己来？"
-   > - **A. 你帮我改** — AI 执行 ufw 命令
-   > - **B. 我自己改** — 输出规则清单，用户手工执行
+   > "Firewall rules are ready. Should I apply them directly, or will you do it yourself?"
+   > - **A. You apply them** — AI runs ufw commands
+   > - **B. I'll do it myself** — output rule list, user executes manually
 
 ## Planned rules (output before executing)
 

package/bundled/skills-windows/prizmkit-deploy/references/ssh-execution-flow.md

@@ -4,7 +4,7 @@ Pipeline runs in strict order. Each group must complete before the next begins.
 
 ## Pre-flight — Change Summary
 
-Show what will be deployed using `git log --oneline <last-deployed-commit>..HEAD`. If first deployment, show last 5 commits. If no new commits, warn "没有新的代码变更。确定要重新部署吗？"
+Show what will be deployed using `git log --oneline <last-deployed-commit>..HEAD`. If first deployment, show last 5 commits. If no new commits, warn "No new code changes. Are you sure you want to redeploy?"
 
 ## Group 1 — Pre-flight & Prepare
 

package/bundled/skills-windows/prizmkit-deploy/references/ssl-setup.md

@@ -15,11 +15,11 @@ Also check `/etc/hostname` for vendor patterns.
 ## Step 2 — Choose SSL strategy
 
 - **Cloud vendor detected** → ask user:
-  > "检测到服务器运行在 <云厂商>。用哪种 SSL 方案？"
-  > - **A. Let's Encrypt 免费证书（推荐）** — 一行命令永久自动续期，最省心
-  > - **B. <云厂商> 自有证书** — 需手动下载配置，1年有效期需手动续期
+  > "Detected the server is running on <cloud-vendor>. Which SSL approach?"
+  > - **A. Let's Encrypt free certificate (recommended)** — one command for permanent auto-renewal, hassle-free
+  > - **B. <cloud-vendor> native certificate** — manual download/config, 1-year validity requires manual renewal
   >
-  > 选 A 我直接帮你搞定；选 B 你需要在云控制台下载证书后告诉我路径。
+  > Choose A and I'll set it up for you; choose B and you'll need to download the certificate from the cloud console and tell me the path.
 - **No cloud vendor / unknown** → use certbot directly, no choice needed.
 
 ## Step 3 — Certbot install & certificate request

package/bundled/skills-windows/prizmkit-prizm-docs/assets/prizm-docs-format.md

@@ -544,7 +544,7 @@ JSON:
   "hooks": {
     "UserPromptSubmit": [
       {
-        "matcher": "(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b|提交|推送|收尾|完成任务|合并|发版|发布",
+        "matcher": "(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b",
         "hooks": [
           {
             "type": "command",

package/bundled/skills-windows/prizmkit-test/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-test"
-description: "Full-stack test generation and orchestration. Detects architecture, discovers/runs existing tests, analyzes coverage gaps, generates missing unit/integration/E2E tests including business-specific boundary cases, validates every interface with a required boundary coverage matrix, and outputs a unified report. Use after completing development to verify quality before deploy. Trigger on: 'test', 'run tests', 'check quality', 'verify code', 'generate tests', 'test coverage', 'fill test gaps', 'boundary tests', 'edge cases', 'quality check', '测试', '验证', '跑测试', '补测试', '边界测试'. (project)"
+description: "Full-stack test generation and orchestration. Detects architecture, discovers/runs existing tests, analyzes coverage gaps, generates missing unit/integration/E2E tests including business-specific boundary cases, validates every interface with a required boundary coverage matrix, and outputs a unified report. Use after completing development to verify quality before deploy. Trigger on: 'test', 'run tests', 'check quality', 'verify code', 'generate tests', 'test coverage', 'fill test gaps', 'boundary tests', 'edge cases', 'quality check', 'add tests'. (project)"
 ---
 
 # PrizmKit Test
@@ -11,7 +11,7 @@ A comprehensive test generation and orchestration skill. Discovers existing test
 - After completing one or more features/refactors/bugfixes
 - As a quality gate before deploy
 - Project has a test framework installed but zero tests written (first-time test generation)
-- User says "test", "run tests", "verify", "check quality", "补测试"
+- User says "test", "run tests", "verify", "check quality", "add tests"
 
 ### When NOT to Use
 - Project has no test framework AND no code to test

package/bundled/skills-windows/recovery-workflow/evals/evals.json

@@ -5,7 +5,7 @@
     {
       "id": 1,
       "name": "bugfix-mid-fix",
-      "prompt": "session 断了，帮我恢复一下",
+      "prompt": "My session broke, help me recover",
       "expected_output": "Should auto-detect bug-fix-workflow from fix/B-001-* branch. Should detect fix-plan.md + code changes → infer Phase 5 (Review). Should display recovery report with workflow type, phase, artifacts, code stats. After user confirms, should invoke /prizmkit-code-review on existing changes.",
       "setup_description": "Create fix/B-001-login-crash branch, .prizmkit/bugfix/B-001/fix-plan.md, modify 3 source files + 1 test file. No fix-report.md, no commits ahead of main.",
       "files": []
@@ -13,7 +13,7 @@
     {
       "id": 2,
       "name": "bugfix-plan-only",
-      "prompt": "继续之前的工作",
+      "prompt": "Continue the previous work",
       "expected_output": "Should auto-detect bug-fix-workflow from fix/B-002-* branch. Should detect fix-plan.md but no code changes → infer Phase 4 (Fix). Should read fix-plan.md and start implementing the fix.",
       "setup_description": "Create fix/B-002-null-pointer branch, .prizmkit/bugfix/B-002/fix-plan.md with diagnosis and fix approach. No code changes.",
       "files": []
@@ -37,7 +37,7 @@
     {
       "id": 5,
       "name": "no-workflow-detected",
-      "prompt": "恢复",
+      "prompt": "recover",
       "expected_output": "Should detect no workflow signatures in workspace. Should display guidance message suggesting /feature-workflow, /bug-fix-workflow, or /refactor-workflow. Should NOT attempt any recovery actions.",
       "setup_description": "Clean workspace on main branch. No .prizmkit/plans/feature-list.json, no bug-fix artifacts, no .prizmkit/plans/refactor-list.json, no fix/* or feat/* or refactor/* branches.",
       "files": []

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

@@ -1,33 +1,33 @@
 {
   "name": "prizm-dev-team",
   "team_name": "prizm-dev-team",
-  "description": "PrizmKit-integrated Multi-Agent software development team. 3 specialized agents (Dev, Reviewer, Critic) following PrizmKit spec-driven workflow with pipeline and checkpoints.",
+  "description": "PrizmKit-integrated Multi-Agent software development team. 3 specialized agents (Dev, Reviewer, Critic) following PrizmKit spec-driven workflow. Critic supports parallel 3-critic voting with distinct focus lenses.",
   "lead": "orchestrator",
   "communication": {
     "protocol": "SendMessage",
     "routing": "mesh",
-    "note": "Teammates communicate directly via SendMessage; key messages must also be sent to Orchestrator (the main agent session)"
+    "note": "Teammates communicate directly via SendMessage; key messages must also be sent to Orchestrator (the main AI session). Critic agents operate independently in parallel — they do NOT read each other's reports."
   },
   "members": [
     {
       "name": "dev",
-      "role": "developer", 
+      "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 .prizmkit/prizm-docs/ TRAPS before implementing.",
+      "prompt": "You are a Dev Agent of the prizm-dev-team. Your complete behavior rules are in your agent definition. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x].",
       "subscriptions": ["*"]
     },
     {
       "name": "reviewer",
       "role": "reviewer",
       "agentDefinition": "prizm-dev-team-reviewer",
-      "prompt": "You are the Reviewer Agent of the prizm-dev-team. Run /prizmkit-code-review for diagnosis + fix strategy formulation, write and execute integration tests. Produce structured Fix Instructions (Root Cause, Impact, Fix Strategy, Code Guidance, Verification) so Dev can follow them precisely. review-report.md is written to the artifact directory by /prizmkit-code-review.",
+      "prompt": "You are the Reviewer Agent of the prizm-dev-team. Your complete behavior rules are in your agent definition. Run /prizmkit-code-review for diagnosis + fix strategy formulation. You do NOT run tests — the Orchestrator handles testing.",
       "subscriptions": ["*"]
     },
     {
       "name": "critic",
       "role": "critic",
       "agentDefinition": "prizm-dev-team-critic",
-      "prompt": "You are the Critic Agent of the prizm-dev-team. Challenge plans and implementations for project fitness, style consistency, robustness, and integration quality. Do NOT verify correctness — that is the Reviewer's job. Write challenge-report.md with adversarial findings.",
+      "prompt": "You are the Critic Agent of the prizm-dev-team. Your complete behavior rules are in your agent definition. Challenge plans and implementations for project fitness, style consistency, robustness, and integration quality. Supports parallel 3-critic voting mode. Do NOT verify correctness — that is the Reviewer's job.",
       "subscriptions": ["*"]
     }
   ]

package/package.json

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