ccg-workflow 1.7.51 → 1.7.53

package/README.md

@@ -43,34 +43,36 @@ npx ccg-workflow
 | `/ccg:worktree` | Worktree 管理 |
 | `/ccg:init` | 初始化 CLAUDE.md |
 | `/ccg:enhance` | Prompt 增强 |
-| `/ccg:spec-init` | 初始化 OpenSpec 环境 |
-| `/ccg:spec-research` | 需求 → 约束集 |
-| `/ccg:spec-plan` | 约束 → 零决策计划 |
-| `/ccg:spec-impl` | 按计划执行 + 归档 |
-| `/ccg:spec-review` | 双模型交叉审查 |
 
-### OpenSpec 规范驱动（v1.7.48）
+**注意**：v1.7.52 起，`/ccg:spec-*` 命令已迁移到 OPSX 架构。请使用 `/opsx:*` 命令代替：
+- `/opsx:init` - 初始化 OPSX 环境
+- `/opsx:research` - 需求 → 约束集
+- `/opsx:plan` - 约束 → 零决策计划
+- `/opsx:impl` - 按计划执行 + 归档
+- `/opsx:review` - 双模型交叉审查
 
-集成 [OpenSpec](https://github.com/fission-ai/openspec)，把需求变成约束，让 AI 没法自由发挥：
+### OPSX 规范驱动（v1.7.52+）
+
+集成 [OPSX 架构](https://github.com/fission-ai/opsx)，把需求变成约束，让 AI 没法自由发挥：
 
 ```bash
 # 初始化
-/ccg:spec-init
+/opsx:init
 
 # 研究需求 → 输出约束集
-/ccg:spec-research 实现用户认证
+/opsx:research 实现用户认证
 
 # 并行分析 → 零决策计划
-/ccg:spec-plan
+/opsx:plan
 
 # 按计划执行
-/ccg:spec-impl
+/opsx:impl
 
 # 独立审查（随时可用）
-/ccg:spec-review
+/opsx:review
 ```
 
-每阶段之间可 `/clear`，状态存在 `openspec/` 目录，不怕上下文爆。
+**重要**：v1.7.52 起，旧的 `/ccg:spec-*` 命令已废弃，请使用 `/opsx:*` 命令。每阶段之间可 `/clear`，状态存在 `opsx/` 目录，不怕上下文爆。
 
 ### 规划与执行分离
 
@@ -187,4 +189,4 @@ MIT
 
 ---
 
-v1.7.48 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)
+v1.7.52 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)

package/dist/cli.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import cac from 'cac';
 import ansis from 'ansis';
-import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, s as showMainMenu, i as init, E as configMcp, F as version, a as i18n } from './shared/ccg-workflow.CEsTETSi.mjs';
+import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, s as showMainMenu, i as init, E as configMcp, F as version, a as i18n } from './shared/ccg-workflow.SwZf2ogk.mjs';
 import 'inquirer';
 import 'node:child_process';
 import 'node:util';

package/dist/index.mjs

@@ -1,4 +1,4 @@
-export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.CEsTETSi.mjs';
+export { c as changeLanguage, x as checkForUpdates, y as compareVersions, d as createDefaultConfig, e as createDefaultRouting, g as getCcgDir, f as getConfigPath, t as getCurrentVersion, v as getLatestVersion, j as getWorkflowById, h as getWorkflowConfigs, a as i18n, i as init, b as initI18n, l as installAceTool, m as installAceToolRs, k as installWorkflows, p as migrateToV1_4_0, q as needsMigration, r as readCcgConfig, s as showMainMenu, o as uninstallAceTool, n as uninstallWorkflows, u as update, w as writeCcgConfig } from './shared/ccg-workflow.SwZf2ogk.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.CEsTETSi.mjs → ccg-workflow.SwZf2ogk.mjs}

@@ -10,7 +10,7 @@ import i18next from 'i18next';
 import ora from 'ora';
 import { parse, stringify } from 'smol-toml';
 
-const version = "1.7.51";
+const version = "1.7.53";
 
 function isWindows() {
   return process.platform === "win32";
@@ -1863,20 +1863,23 @@ async function update() {
     }
     console.log();
     const effectiveNeedsUpdate = hasUpdate || needsWorkflowUpdate;
+    let defaultConfirm = effectiveNeedsUpdate;
     let message;
     if (hasUpdate) {
-      message = `\u786E\u8BA4\u8981\u66F4\u65B0\u5230 v${latestVersion} \u5417\uFF1F\uFF08\u5148\u4E0B\u8F7D\u6700\u65B0\u5305 \u2192 \u5220\u9664\u65E7\u5DE5\u4F5C\u6D41 \u2192 \u5B89\u88C5\u65B0\u5DE5\u4F5C\u6D41\uFF09`;
+      message = `\u53D1\u73B0\u65B0\u7248\u672C v${latestVersion} (\u5F53\u524D: v${currentVersion})\uFF0C\u662F\u5426\u66F4\u65B0\uFF1F`;
+      defaultConfirm = true;
     } else if (needsWorkflowUpdate) {
       message = `\u68C0\u6D4B\u5230\u672C\u5730\u5DE5\u4F5C\u6D41\u7248\u672C (v${localVersion}) \u4F4E\u4E8E\u5F53\u524D\u7248\u672C (v${currentVersion})\uFF0C\u662F\u5426\u66F4\u65B0\uFF1F`;
+      defaultConfirm = true;
     } else {
-      message = "\u5F53\u524D\u5DF2\u662F\u6700\u65B0\u7248\u672C\u3002\u8981\u91CD\u65B0\u5B89\u88C5\u5417\uFF1F\uFF08\u5148\u4E0B\u8F7D\u6700\u65B0\u5305 \u2192 \u5220\u9664\u65E7\u5DE5\u4F5C\u6D41 \u2192 \u5B89\u88C5\u65B0\u5DE5\u4F5C\u6D41\uFF09";
+      message = `\u5F53\u524D\u5DF2\u662F\u6700\u65B0\u7248\u672C (v${currentVersion})\u3002\u662F\u5426\u5F3A\u5236\u91CD\u65B0\u5B89\u88C5/\u4FEE\u590D\u5DE5\u4F5C\u6D41\uFF1F`;
+      defaultConfirm = false;
     }
     const { confirmUpdate } = await inquirer.prompt([{
       type: "confirm",
       name: "confirmUpdate",
       message,
-      default: effectiveNeedsUpdate
-      // Default to true if needs update
+      default: defaultConfirm
     }]);
     if (!confirmUpdate) {
       console.log(ansis.gray("\u5DF2\u53D6\u6D88\u66F4\u65B0"));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccg-workflow",
-  "version": "1.7.51",
+  "version": "1.7.53",
   "description": "Claude-Codex-Gemini 多模型协作系统 - 智能路由多模型开发工作流",
   "type": "module",
   "packageManager": "pnpm@10.17.1",

package/templates/commands/spec-impl.md

@@ -12,16 +12,17 @@ description: '按规范执行 + 多模型协作 + 归档'
 - **NEVER** apply Codex/Gemini prototypes directly—all outputs are reference only.
 - **MANDATORY**: Request `unified diff patch` format from external models; they have zero write permission.
 - Keep implementation strictly within `tasks.md` scope—no scope creep.
-- Refer to `openspec/AGENTS.md` for conventions.
+- Refer to `openspec/config.yaml` for conventions.
 
 **Steps**
-1. **Select Proposal**
-   - Run `openspec list` to inspect Active Changes.
-   - Confirm with user which proposal ID to implement.
-   - Run `openspec show <proposal_id>` to review tasks.
+1. **Select Change**
+   - Run `/opsx:list` to inspect Active Changes.
+   - Confirm with user which change ID to implement.
+   - Run `/opsx:show <change_id>` to review tasks.
 
-2. **Apply OpenSpec Change**
-   - Run `/openspec:apply <proposal_id>` to enter implementation mode.
+2. **Apply OPSX Change**
+   - Use `/ccg:spec-impl` (which uses OpenSpec skills internally) to enter implementation mode.
+   - This skill will guide you through the tasks defined in `tasks.md`.
 
 3. **Identify Minimal Verifiable Phase**
    - Review `tasks.md` and identify the **smallest verifiable phase**.
@@ -104,13 +105,13 @@ description: '按规范执行 + 多模型协作 + 归档'
 
 10. **Archive on Completion**
     - When ALL tasks in `tasks.md` are marked `[x]`:
-    - Run `/openspec:archive <proposal_id>`
+    - The agent will use OpenSpec skills to archive the change.
     - This merges spec deltas to `openspec/specs/` and moves change to archive.
 
 **Reference**
-- Check task status: `openspec show <id>`
-- Validate before archive: `openspec validate <id>`
-- View active changes: `openspec list`
+- Check task status: `/opsx:show <id>`
+- Validate before archive: `/opsx:validate <id>`
+- View active changes: `/opsx:list`
 - Search existing patterns: `rg -n "function|class" <file>`
 
 **Exit Criteria**
@@ -118,6 +119,5 @@ Implementation is complete when:
 - [ ] All tasks in `tasks.md` marked `[x]`
 - [ ] All multi-model reviews passed
 - [ ] Side-effect review confirmed no regressions
-- [ ] `openspec validate <id>` returns zero issues
 - [ ] Change archived successfully
 <!-- CCG:SPEC:IMPL:END -->

package/templates/commands/spec-init.md

@@ -1,9 +1,9 @@
 ---
-description: '初始化 OpenSpec 环境 + 验证多模型 MCP 工具'
+description: '初始化 OpenSpec (OPSX) 环境 + 验证多模型 MCP 工具'
 ---
 <!-- CCG:SPEC:INIT:START -->
 **Core Philosophy**
-- OpenSpec provides the specification framework; CCG adds multi-model collaboration.
+- OPSX provides the specification framework; CCG adds multi-model collaboration.
 - This phase ensures all tools are ready before any development work begins.
 - Fail fast: detect missing dependencies early rather than mid-workflow.
 
@@ -18,20 +18,26 @@ description: '初始化 OpenSpec 环境 + 验证多模型 MCP 工具'
    - Identify OS using `uname -s` (Unix) or environment variables (Windows).
    - Inform user which OS was detected.
 
-2. **Check and Install OpenSpec**
-   - Verify if `openspec` CLI is installed: `openspec --version`
-   - If not installed:
+2. **Check and Install OPSX**
+   - Verify if OPSX commands are available: `/opsx:version`
+   - If not installed or not found:
      ```bash
-     npm install -g @fission-ai/openspec@latest
+     npm install -g @opsx/cli@latest
      ```
-   - Confirm installation success.
+   - **Path Verification**:
+     - If `/opsx:version` command is not found after installation:
+       1. Ensure Claude Code commands are properly loaded
+       2. Restart Claude Code session if needed
+       3. Check if OPSX skills are installed in `.claude/skills/`
+   - Confirm installation success by running `/opsx:version` again.
 
-3. **Initialize OpenSpec for Current Project**
+3. **Initialize OPSX for Current Project**
    - Run:
      ```bash
-     openspec init --tools claude
+     /opsx:init --tools claude
      ```
    - Verify `openspec/` directory structure is created.
+   - Verify `.claude/skills/` contains `opsx-*` skills.
    - Report any errors with remediation steps.
 
 4. **Validate Multi-Model MCP Tools**
@@ -47,26 +53,39 @@ description: '初始化 OpenSpec 环境 + 验证多模型 MCP 工具'
    - For each unavailable tool, display warning with installation instructions.
 
 5. **Validate Context Retrieval MCP** (Optional)
-   - Check if `mcp__ace-tool__search_context` is available.
-   - If not, suggest: "Run `npx ccg-workflow` and select ace-tool MCP option."
+   - **Check Active Tool**: Is `mcp__ace-tool__search_context` available in the current session?
+   - **Check Configuration**: If tool is missing, check `~/.claude.json` (or `%APPDATA%\Claude\claude.json` on Windows) for `"ace-tool"` or `"ace-tool-rs"` in `mcpServers`.
+   - **Diagnosis**:
+     - If tool available: Mark as "✓ Active".
+     - If config exists but tool missing: Mark as "⚠️ Configured but inactive (Try restarting Claude)".
+     - If neither: Mark as "○ Not installed (Optional)".
+   - If not installed/configured, suggest: "Run `npx ccg-workflow` and select ace-tool MCP option."
 
 6. **Summary Report**
    Display status table:
    ```
    Component                 Status
    ─────────────────────────────────
-   OpenSpec CLI              ✓/✗
+   OPSX CLI                  ✓/✗
    Project initialized       ✓/✗
+   OPSX Skills               ✓/✗
    codeagent-wrapper         ✓/✗
    Codex backend             ✓/✗
    Gemini backend            ✓/✗
    ace-tool MCP              ✓/✗ (optional)
    ```
-   If any required components missing, list actions before proceeding.
+
+   **Next Steps (Use CCG Encapsulated Commands)**
+   1. Start Research: `/ccg:spec-research "description"`
+   2. Plan & Design: `/ccg:spec-plan`
+   3. Implement: `/ccg:spec-impl` (Includes auto-review & archive)
+
+   **Standalone Tools (Available Anytime)**
+   - Code Review: `/ccg:spec-review` (Independent dual-model review)
 
 **Reference**
-- OpenSpec CLI: `openspec --help`
+- OPSX CLI: `/opsx:help`
 - CCG Workflow: `npx ccg-workflow`
 - Codex/Gemini MCP: Bundled with codeagent-wrapper
-- Node.js >= 18.x required for OpenSpec
+- Node.js >= 18.x required for OPSX
 <!-- CCG:SPEC:INIT:END -->

package/templates/commands/spec-plan.md

@@ -12,13 +12,13 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
 - Do not proceed to implementation until every ambiguity is resolved.
 - Multi-model collaboration is **mandatory**: use both Codex and Gemini.
 - If constraints cannot be fully specified, escalate to user or return to research phase.
-- Refer to `openspec/AGENTS.md` for conventions; run `openspec update` if missing.
+- Refer to `openspec/config.yaml` for project conventions.
 
 **Steps**
-1. **Select Proposal**
-   - Run `openspec list` to display Active Changes.
-   - Confirm with user which proposal ID to refine.
-   - Run `openspec show <proposal_id>` to review current state.
+1. **Select Change**
+   - Run `/opsx:list` to display Active Changes.
+   - Confirm with user which change ID to refine.
+   - Run `/opsx:status <change_id>` to review current state.
 
 2. **Multi-Model Implementation Analysis (PARALLEL)**
    - **CRITICAL**: You MUST launch BOTH Codex AND Gemini in a SINGLE message with TWO Bash tool calls.
@@ -29,7 +29,7 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
    **FIRST Bash call (Codex)**:
    ```
    Bash({
-     command: "~/.claude/bin/codeagent-wrapper --backend codex - \"$PWD\" <<'EOF'\nAnalyze proposal <proposal_id> from backend perspective:\n- Implementation approach\n- Technical risks\n- Alternative architectures\n- Edge cases and failure modes\nOUTPUT: JSON with analysis\nEOF",
+     command: "~/.claude/bin/codeagent-wrapper --backend codex - \"$PWD\" <<'EOF'\nAnalyze change <change_id> from backend perspective:\n- Implementation approach\n- Technical risks\n- Alternative architectures\n- Edge cases and failure modes\nOUTPUT: JSON with analysis\nEOF",
      run_in_background: true,
      timeout: 300000,
      description: "Codex: backend analysis"
@@ -39,7 +39,7 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
    **SECOND Bash call (Gemini) - IN THE SAME MESSAGE**:
    ```
    Bash({
-     command: "~/.claude/bin/codeagent-wrapper --backend gemini - \"$PWD\" <<'EOF'\nAnalyze proposal <proposal_id> from frontend/integration perspective:\n- Maintainability assessment\n- Scalability considerations\n- Integration conflicts\nOUTPUT: JSON with analysis\nEOF",
+     command: "~/.claude/bin/codeagent-wrapper --backend gemini - \"$PWD\" <<'EOF'\nAnalyze change <change_id> from frontend/integration perspective:\n- Maintainability assessment\n- Scalability considerations\n- Integration conflicts\nOUTPUT: JSON with analysis\nEOF",
      run_in_background: true,
      timeout: 300000,
      description: "Gemini: frontend analysis"
@@ -82,28 +82,28 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
    - **Monotonicity**: Ordering guarantees (e.g., timestamps increase)
    - **Bounds**: Value ranges, size limits, rate constraints
 
-5. **Update OpenSpec Documents**
-   - Run `/openspec:proposal <proposal_id>` to update specs with:
-     * All resolved constraints
-     * PBT properties in spec format
-     * Zero-decision task sequence
-   - Run `openspec validate <proposal_id>` to verify format.
+5. **Update OPSX Artifacts**
+   - The agent will use OpenSpec skills to generate/update:
+     * specs (Requirements + PBT)
+     * design (Technical decisions)
+     * tasks (Zero-decision implementation plan)
+   - Ensure all resolved constraints and PBT properties are included in the generated artifacts.
 
 6. **Context Checkpoint**
    - Report current context usage.
-   - If approaching 80K tokens, suggest: "Run `/clear` and continue with `/ccg:spec:impl`"
+   - If approaching 80K tokens, suggest: "Run `/clear` and continue with `/ccg:spec-impl`"
 
 **Exit Criteria**
-A proposal is ready for implementation only when:
+A change is ready for implementation only when:
 - [ ] All multi-model analyses completed and synthesized
 - [ ] Zero ambiguities remain (verified by step 3 audit)
 - [ ] All PBT properties documented with falsification strategies
-- [ ] `openspec validate <id>` returns zero issues
+- [ ] Artifacts (specs, design, tasks) generated via OpenSpec skills
 - [ ] User has explicitly approved all constraint decisions
 
 **Reference**
-- Inspect proposal: `openspec show <id> --json`
-- Check conflicts: `openspec list --specs`
+- Inspect change: `/opsx:status <id>`
+- Check conflicts: `/opsx:schemas`
 - Search patterns: `rg -n "INVARIANT:|PROPERTY:" openspec/`
 - Use `AskUserQuestion` for ANY ambiguity—never assume
 <!-- CCG:SPEC:PLAN:END -->

package/templates/commands/spec-research.md

@@ -1,12 +1,12 @@
 ---
-description: '需求 → 约束集（并行探索 + OpenSpec 提案）'
+description: '需求 → 约束集（并行探索 + OPSX 提案）'
 ---
 <!-- CCG:SPEC:RESEARCH:START -->
 **Core Philosophy**
 - Research produces **constraint sets**, not information dumps. Each constraint narrows the solution space.
 - Constraints tell subsequent stages "don't consider this direction," enabling mechanical execution without decisions.
 - Output: 约束集合 + 可验证的成功判据 (constraint sets + verifiable success criteria).
-- Strictly adhere to OpenSpec rules when writing spec-structured documents.
+- Strictly adhere to OPSX rules when writing spec-structured documents.
 
 **Guardrails**
 - **STOP! BEFORE ANY OTHER ACTION**: You MUST call `mcp__ace-tool__enhance_prompt` FIRST. This is NON-NEGOTIABLE.
@@ -30,9 +30,13 @@ description: '需求 → 约束集（并行探索 + OpenSpec 提案）'
    - Wait for enhanced prompt result.
    - Use enhanced prompt for ALL subsequent steps.
 
-1. **Generate OpenSpec Proposal**
-   - Run: `/openspec:proposal $ARGUMENTS`
-   - This scaffolds `openspec/changes/<name>/` with proposal.md, tasks.md, specs/.
+1. **Generate OPSX Change**
+   - Create a new change using OPSX command:
+     ```bash
+     /opsx:new "<brief-descriptive-name>"
+     ```
+   - This scaffolds `openspec/changes/<name>/` with proposal.md.
+   - If change already exists, use `/opsx:list` to find it and continue.
 
 2. **Initial Codebase Assessment**
    - Use `mcp__ace-tool__search_context` to scan codebase.
@@ -78,8 +82,8 @@ description: '需求 → 约束集（并行探索 + OpenSpec 提案）'
      * Suggest defaults when applicable
    - Capture responses as additional constraints.
 
-7. **Finalize OpenSpec Proposal**
-   - Transform constraint sets into OpenSpec format:
+7. **Finalize OPSX Proposal**
+   - Transform constraint sets into OPSX format:
      * **Context**: User need + discovered constraints
      * **Requirements**: Each constraint becomes requirement with scenario
      * **Success Criteria**: Derived from hints and user confirmations
@@ -91,11 +95,10 @@ description: '需求 → 约束集（并行探索 + OpenSpec 提案）'
 
 8. **Context Checkpoint**
    - Report current context usage.
-   - If approaching 80K tokens, suggest: "Run `/clear` and continue with `/ccg:spec:plan`"
+   - If approaching 80K tokens, suggest: "Run `/clear` and continue with `/ccg:spec-plan`"
 
 **Reference**
-- Review constraints: `rg -n "Constraint:|MUST|MUST NOT" openspec/specs`
+- OPSX CLI: `/opsx:status`, `/opsx:show`
 - Check prior research: `ls openspec/changes/*/`
-- Use `openspec show <name>` to inspect proposal structure
 - Use `AskUserQuestion` for ANY ambiguity—never assume or guess
 <!-- CCG:SPEC:RESEARCH:END -->

package/templates/commands/spec-review.md

@@ -15,13 +15,13 @@ description: '双模型交叉审查（独立工具，随时可用）'
 
 **Steps**
 1. **Select Proposal**
-   - Run `openspec list` to display Active Changes.
+   - Run `/opsx:list` to display Active Changes.
    - Confirm with user which proposal ID to review.
-   - Run `openspec show <proposal_id>` to load spec and tasks.
+   - Run `/opsx:show <proposal_id>` to load spec and tasks.
 
 2. **Collect Implementation Artifacts**
    - Identify all files modified by this proposal.
-   - Use `git diff` or `openspec diff <proposal_id>` to get change summary.
+   - Use `git diff` or `/opsx:diff <proposal_id>` to get change summary.
    - Load relevant spec constraints and PBT properties from `openspec/changes/<id>/specs/`.
 
 3. **Multi-Model Review (PARALLEL)**
@@ -113,8 +113,8 @@ Review is complete when:
 - [ ] User decision captured (archive / return to impl / defer)
 
 **Reference**
-- View proposal: `openspec show <id>`
+- View proposal: `/opsx:show <id>`
 - Check spec constraints: `rg -n "CONSTRAINT:|MUST|INVARIANT:" openspec/changes/<id>/specs/`
-- View implementation diff: `openspec diff <id>` or `git diff`
+- View implementation diff: `/opsx:diff <id>` or `git diff`
 - Archive (after passing): `/ccg:spec-impl` → Step 10
 <!-- CCG:SPEC:REVIEW:END -->