ccg-workflow 1.7.62 → 1.7.63

package/README.md

@@ -237,4 +237,4 @@ MIT
 
 ---
 
-v1.7.62 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)
+v1.7.63 | [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.DbiYrRv1.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.CJlHAzd-.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.DbiYrRv1.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.CJlHAzd-.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.DbiYrRv1.mjs → ccg-workflow.CJlHAzd-.mjs}

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

package/package.json

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

package/templates/commands/spec-impl.md

@@ -109,12 +109,14 @@ description: '按规范执行 + 多模型协作 + 归档'
 
 10. **Archive on Completion**
     - When ALL tasks in `tasks.md` are marked `[x]`:
+    - **Verify first (v1.2+)**: Use `/opsx:verify` to validate implementation matches artifacts.
     - 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 status --change "<id>" --json`
 - View active changes: `openspec list --json`
+- Verify before archive (v1.2+): `/opsx:verify`
 - Search existing patterns: `rg -n "function|class" <file>`
 
 **Exit Criteria**

package/templates/commands/spec-init.md

@@ -43,10 +43,14 @@ description: '初始化 OpenSpec (OPSX) 环境 + 验证多模型 MCP 工具'
      ```bash
      ls -la openspec/ .claude/skills/openspec-* 2>/dev/null || echo "Not initialized"
      ```
-   - If not initialized, run:
+   - If not initialized, run interactive setup (v1.2+ auto-detects AI tools):
      ```bash
-     npx @fission-ai/openspec init --tools claude
+     npx @fission-ai/openspec init
      ```
+   - **Profile Selection** (v1.2+):
+     - `core` profile (default): 4 essential workflows (`propose`, `explore`, `apply`, `archive`)
+     - `custom` profile: Pick any subset of workflows
+     - To change profile later: `openspec config profile`
    - Verify initialization:
      - Check `openspec/` directory exists
      - Check `.claude/skills/` contains `openspec-*` skills
@@ -99,7 +103,8 @@ description: '初始化 OpenSpec (OPSX) 环境 + 验证多模型 MCP 工具'
 
 **Reference**
 - OpenSpec (OPSX) CLI: `npx @fission-ai/openspec --help`
-- OPSX Commands: `/opsx:new`, `/opsx:continue`, `/opsx:apply`, etc.
+- OPSX Commands (v1.2+): `/opsx:propose` (one-step), `/opsx:explore`, `/opsx:new`, `/opsx:ff`, `/opsx:apply`, `/opsx:verify`, `/opsx:archive`
+- Profile Management: `openspec config profile`
 - 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

@@ -88,6 +88,7 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
      * specs (Requirements + PBT)
      * design (Technical decisions)
      * tasks (Zero-decision implementation plan)
+   - **Fast-Forward Option (v1.2+)**: Use `/opsx:ff` to generate all planning artifacts at once instead of step-by-step with `/opsx:continue`.
    - Ensure all resolved constraints and PBT properties are included in the generated artifacts.
 
 6. **Context Checkpoint**
@@ -105,6 +106,7 @@ A change is ready for implementation only when:
 **Reference**
 - Inspect change: `openspec status --change "<id>" --json`
 - List changes: `openspec list --json`
+- Fast-forward artifacts (v1.2+): `/opsx:ff` — creates all planning artifacts at once
 - Search patterns: `rg -n "INVARIANT:|PROPERTY:" openspec/`
 - Use `AskUserQuestion` for ANY ambiguity—never assume
 <!-- CCG:SPEC:PLAN:END -->

package/templates/commands/spec-research.md

@@ -27,11 +27,15 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
      ```bash
      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.
+   - **Option A: One-Step Propose (v1.2+ Recommended)**
+     - Use `/opsx:propose` to generate complete proposal (design + specs + tasks) in one step.
+     - This is faster but less iterative.
+   - **Option B: Step-by-Step (More Control)**
+     - 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, continue with existing change.
 
 2. **Initial Codebase Assessment**
@@ -95,6 +99,8 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
 
 **Reference**
 - OPSX CLI: `openspec status --change "<id>" --json`, `openspec list --json`
+- One-step workflow (v1.2+): `/opsx:propose` — generates complete proposal from requirement
+- Step-by-step workflow: `/opsx:new` → `/opsx:continue` or `/opsx:ff`
 - 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

@@ -11,7 +11,7 @@ description: '双模型交叉审查（独立工具，随时可用）'
 **Guardrails**
 - **MANDATORY**: Both Codex AND Gemini must complete review before synthesis.
 - Review scope is strictly limited to the proposal's changes—no scope creep.
-- Refer to `openspec/AGENTS.md` for spec conventions if reviewing OpenSpec proposals.
+- Refer to `openspec/config.yaml` for project conventions when reviewing OpenSpec proposals.
 
 **Steps**
 1. **Select Proposal**
@@ -117,5 +117,6 @@ Review is complete when:
 - View proposal: `openspec status --change "<id>" --json`
 - Check spec constraints: `rg -n "CONSTRAINT:|MUST|INVARIANT:" openspec/changes/<id>/specs/`
 - View implementation diff: `git diff`
-- Archive (after passing): `/ccg:spec-impl` → Step 10
+- Verify implementation (v1.2+): `/opsx:verify` — validates implementation matches artifacts
+- Archive (after passing): `/opsx:archive` or `/ccg:spec-impl` → Step 10
 <!-- CCG:SPEC:REVIEW:END -->