ccg-workflow 1.7.55 → 1.7.56

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.Dyysa7hK.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.FSvBGlYq.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.Dyysa7hK.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.FSvBGlYq.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.Dyysa7hK.mjs → ccg-workflow.FSvBGlYq.mjs}

@@ -10,7 +10,7 @@ import i18next from 'i18next';
 import ora from 'ora';
 import { parse, stringify } from 'smol-toml';
 
-const version = "1.7.55";
+const version = "1.7.56";
 
 function isWindows() {
   return process.platform === "win32";

package/package.json

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

package/templates/commands/spec-impl.md

@@ -16,9 +16,9 @@ description: '按规范执行 + 多模型协作 + 归档'
 
 **Steps**
 1. **Select Change**
-   - Run `/opsx:list` to inspect Active Changes.
+   - Run `openspec list --json` to inspect Active Changes.
    - Confirm with user which change ID to implement.
-   - Run `/opsx:show <change_id>` to review tasks.
+   - Run `openspec status --change "<change_id>" --json` to review tasks.
 
 2. **Apply OPSX Change**
    - Use `/ccg:spec-impl` (which uses OpenSpec skills internally) to enter implementation mode.
@@ -111,9 +111,8 @@ description: '按规范执行 + 多模型协作 + 归档'
     - This merges spec deltas to `openspec/specs/` and moves change to archive.
 
 **Reference**
-- Check task status: `/opsx:show <id>`
-- Validate before archive: `/opsx:validate <id>`
-- View active changes: `/opsx:list`
+- Check task status: `openspec status --change "<id>" --json`
+- View active changes: `openspec list --json`
 - Search existing patterns: `rg -n "function|class" <file>`
 
 **Exit Criteria**

package/templates/commands/spec-init.md

@@ -19,25 +19,38 @@ description: '初始化 OpenSpec (OPSX) 环境 + 验证多模型 MCP 工具'
    - Inform user which OS was detected.
 
 2. **Check and Install OpenSpec (OPSX)**
-   - Verify if OPSX commands are available: `/opsx:version`
-   - If not installed or not found:
+   - **IMPORTANT**: OpenSpec CLI command is `openspec`, NOT `opsx`
+   - Verify if OpenSpec is available:
+     ```bash
+     npx @fission-ai/openspec --version
+     ```
+   - If not found, install globally:
      ```bash
      npm install -g @fission-ai/openspec@latest
      ```
-   - **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.
+   - After installation, verify again:
+     ```bash
+     openspec --version
+     ```
+   - If `openspec` command not found after global install, use `npx`:
+     ```bash
+     npx @fission-ai/openspec --version
+     ```
+   - **Note**: Always use `openspec` (not `opsx`) for CLI commands.
 
 3. **Initialize OPSX for Current Project**
-   - Run:
+   - Check if already initialized:
+     ```bash
+     ls -la openspec/ .claude/skills/openspec-* 2>/dev/null || echo "Not initialized"
+     ```
+   - If not initialized, run:
      ```bash
-     /opsx:init --tools claude
+     npx @fission-ai/openspec init --tools claude
      ```
-   - Verify `openspec/` directory structure is created.
-   - Verify `.claude/skills/` contains `opsx-*` skills.
+   - Verify initialization:
+     - Check `openspec/` directory exists
+     - Check `.claude/skills/` contains `openspec-*` skills
+     - Check `.claude/commands/opsx/` contains OPSX commands
    - Report any errors with remediation steps.
 
 4. **Validate Multi-Model MCP Tools**
@@ -84,7 +97,8 @@ description: '初始化 OpenSpec (OPSX) 环境 + 验证多模型 MCP 工具'
    - Code Review: `/ccg:spec-review` (Independent dual-model review)
 
 **Reference**
-- OpenSpec (OPSX) CLI: `/opsx:help`
+- OpenSpec (OPSX) CLI: `npx @fission-ai/openspec --help`
+- OPSX Commands: `/opsx:new`, `/opsx:continue`, `/opsx:apply`, etc.
 - CCG Workflow: `npx ccg-workflow`
 - Codex/Gemini MCP: Bundled with codeagent-wrapper
 - Node.js >= 18.x required for OpenSpec

package/templates/commands/spec-plan.md

@@ -16,9 +16,9 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
 
 **Steps**
 1. **Select Change**
-   - Run `/opsx:list` to display Active Changes.
+   - Run `openspec list --json` to display Active Changes.
    - Confirm with user which change ID to refine.
-   - Run `/opsx:status <change_id>` to review current state.
+   - Run `openspec status --change "<change_id>" --json` 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.
@@ -102,8 +102,8 @@ A change is ready for implementation only when:
 - [ ] User has explicitly approved all constraint decisions
 
 **Reference**
-- Inspect change: `/opsx:status <id>`
-- Check conflicts: `/opsx:schemas`
+- Inspect change: `openspec status --change "<id>" --json`
+- List changes: `openspec list --json`
 - Search patterns: `rg -n "INVARIANT:|PROPERTY:" openspec/`
 - Use `AskUserQuestion` for ANY ambiguity—never assume
 <!-- CCG:SPEC:PLAN:END -->

package/templates/commands/spec-research.md

@@ -31,12 +31,16 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
    - Use enhanced prompt for ALL subsequent steps.
 
 1. **Generate OPSX Change**
-   - Create a new change using OPSX command:
+   - Check if change already exists:
      ```bash
-     /opsx:new "<brief-descriptive-name>"
+     openspec list --json
+     ```
+   - If change doesn't exist, create it:
+     ```bash
+     openspec new change "<brief-descriptive-name>"
      ```
    - This scaffolds `openspec/changes/<name>/` with proposal.md.
-   - If change already exists, use `/opsx:list` to find it and continue.
+   - If change already exists, continue with existing change.
 
 2. **Initial Codebase Assessment**
    - Use `mcp__ace-tool__search_context` to scan codebase.
@@ -98,7 +102,7 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
    - If approaching 80K tokens, suggest: "Run `/clear` and continue with `/ccg:spec-plan`"
 
 **Reference**
-- OPSX CLI: `/opsx:status`, `/opsx:show`
+- OPSX CLI: `openspec status --change "<id>" --json`, `openspec list --json`
 - Check prior research: `ls openspec/changes/*/`
 - 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 `/opsx:list` to display Active Changes.
+   - Run `openspec list --json` to display Active Changes.
    - Confirm with user which proposal ID to review.
-   - Run `/opsx:show <proposal_id>` to load spec and tasks.
+   - Run `openspec status --change "<proposal_id>" --json` to load spec and tasks.
 
 2. **Collect Implementation Artifacts**
    - Identify all files modified by this proposal.
-   - Use `git diff` or `/opsx:diff <proposal_id>` to get change summary.
+   - Use `git diff` 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: `/opsx:show <id>`
+- View proposal: `openspec status --change "<id>" --json`
 - Check spec constraints: `rg -n "CONSTRAINT:|MUST|INVARIANT:" openspec/changes/<id>/specs/`
-- View implementation diff: `/opsx:diff <id>` or `git diff`
+- View implementation diff: `git diff`
 - Archive (after passing): `/ccg:spec-impl` → Step 10
 <!-- CCG:SPEC:REVIEW:END -->