ccg-workflow 1.7.73 → 1.7.75

package/README.md

@@ -293,4 +293,4 @@ MIT
 
 ---
 
-v1.7.73 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)
+v1.7.75 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)

package/README.zh-CN.md

@@ -295,4 +295,4 @@ MIT
 
 ---
 
-v1.7.73 | [Issues](https://github.com/fengshao1227/ccg-workflow/issues)
+v1.7.75 | [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, a as i18n, s as showMainMenu, i as init, E as configMcp, F as version } from './shared/ccg-workflow.DoPpjMJ6.mjs';
+import { z as diagnoseMcpConfig, A as isWindows, B as readClaudeCodeConfig, C as fixWindowsMcpConfig, D as writeClaudeCodeConfig, r as readCcgConfig, b as initI18n, a as i18n, s as showMainMenu, i as init, E as configMcp, F as version } from './shared/ccg-workflow.C09usDEA.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.DoPpjMJ6.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.C09usDEA.mjs';
 import 'ansis';
 import 'inquirer';
 import 'node:child_process';

package/dist/shared/{ccg-workflow.DoPpjMJ6.mjs → ccg-workflow.C09usDEA.mjs}

@@ -10,7 +10,7 @@ import { parse, stringify } from 'smol-toml';
 import i18next from 'i18next';
 import ora from 'ora';
 
-const version = "1.7.73";
+const version = "1.7.75";
 
 function isWindows() {
   return process.platform === "win32";
@@ -669,9 +669,22 @@ ${workflow.description}
     }
   }
   const skillsTemplateDir = join(templateDir, "skills");
-  const skillsDestDir = join(installDir, "skills");
+  const skillsDestDir = join(installDir, "skills", "ccg");
   if (await fs.pathExists(skillsTemplateDir)) {
     try {
+      const oldSkillsRoot = join(installDir, "skills");
+      const ccgLegacyItems = ["tools", "orchestration", "SKILL.md", "run_skill.js"];
+      const needsMigration = !await fs.pathExists(skillsDestDir) && await fs.pathExists(join(oldSkillsRoot, "tools"));
+      if (needsMigration) {
+        await fs.ensureDir(skillsDestDir);
+        for (const item of ccgLegacyItems) {
+          const oldPath = join(oldSkillsRoot, item);
+          const newPath = join(skillsDestDir, item);
+          if (await fs.pathExists(oldPath)) {
+            await fs.move(oldPath, newPath, { overwrite: true });
+          }
+        }
+      }
       await fs.copy(skillsTemplateDir, skillsDestDir, {
         overwrite: force,
         errorOnExist: false
@@ -756,7 +769,7 @@ async function uninstallWorkflows(installDir) {
   const commandsDir = join(installDir, "commands", "ccg");
   join(installDir, ".ccg", "prompts");
   const agentsDir = join(installDir, "agents", "ccg");
-  const skillsDir = join(installDir, "skills");
+  const skillsDir = join(installDir, "skills", "ccg");
   const binDir = join(installDir, "bin");
   const ccgConfigDir = join(installDir, ".ccg");
   if (await fs.pathExists(commandsDir)) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccg-workflow",
-  "version": "1.7.73",
+  "version": "1.7.75",
   "description": "Claude + Codex + Gemini multi-model collaboration system - smart routing development workflow",
   "type": "module",
   "packageManager": "pnpm@10.17.1",

package/templates/commands/spec-impl.md

@@ -13,6 +13,8 @@ description: '按规范执行 + 多模型协作 + 归档'
 - **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/config.yaml` for conventions.
+- **USER GUIDANCE RULE**: When suggesting next steps to the user, ALWAYS use CCG commands (`/ccg:spec-research`, `/ccg:spec-plan`, `/ccg:spec-impl`, `/ccg:spec-review`). NEVER suggest `/opsx:*` commands to the user. If OpenSpec CLI returns error messages referencing OPSX skills, translate them to CCG equivalents.
+- **TASKS FORMAT RULE**: When generating or modifying `tasks.md`, ALL tasks MUST use checkbox format (`- [ ] X.Y description`). Heading+bullet format will cause OpenSpec CLI to parse 0 tasks and block the workflow.
 
 **Steps**
 1. **Select Change**
@@ -20,12 +22,17 @@ description: '按规范执行 + 多模型协作 + 归档'
    - Confirm with user which change ID to implement.
    - Run `openspec status --change "<change_id>" --json` to review tasks.
 
-2. **Apply OPSX Change**
-   - Call `/opsx:apply` to enter implementation mode:
+2. **Apply OPSX Change (Pre-flight Check)**
+   - Call `/opsx:apply` internally to enter implementation mode:
      ```
      /opsx:apply
      ```
    - This will load the change context and guide you through the tasks defined in `tasks.md`.
+   - **Note**: This is an internal call. If this step fails, guide the user to re-run `/ccg:spec-impl`.
+   - **HARD GATE**: Check the returned `state` field:
+     - If `state: "blocked"` → STOP immediately. Inform the user which artifacts are missing and suggest: "Run `/ccg:spec-plan` to generate missing artifacts first."
+     - If `progress.total === 0` → STOP immediately. Inform: "tasks.md has no parseable tasks. Run `/ccg:spec-plan` to regenerate."
+     - Only proceed to Step 3 when `state: "ready"` and `progress.total > 0`.
 
 3. **Identify Minimal Verifiable Phase**
    - Review `tasks.md` and identify the **smallest verifiable phase**.
@@ -112,11 +119,12 @@ description: '按规范执行 + 多模型协作 + 归档'
 
 10. **Archive on Completion**
     - When ALL tasks in `tasks.md` are marked `[x]`:
-    - Call `/opsx:archive` to archive the change:
+    - Call `/opsx:archive` internally to archive the change:
       ```
       /opsx:archive
       ```
     - This merges spec deltas to `openspec/specs/` and moves change to archive.
+    - **Note**: This is an internal call. If archiving fails, guide the user to re-run `/ccg:spec-impl`.
 
 **Reference**
 - Check task status: `openspec status --change "<id>" --json`

package/templates/commands/spec-plan.md

@@ -13,6 +13,9 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
 - 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/config.yaml` for project conventions.
+- **USER GUIDANCE RULE**: When suggesting next steps to the user, ALWAYS use CCG commands (`/ccg:spec-research`, `/ccg:spec-plan`, `/ccg:spec-impl`, `/ccg:spec-review`). NEVER suggest `/opsx:*` commands to the user. If OpenSpec CLI returns error messages referencing OPSX skills, translate them to CCG equivalents.
+- **TASKS FORMAT RULE**: When generating or modifying `tasks.md`, ALL tasks MUST use checkbox format (`- [ ] X.Y description`). Heading+bullet format will cause OpenSpec CLI to parse 0 tasks and block the workflow.
+- **PHASE BOUNDARY**: This phase ONLY generates OPSX artifacts (specs.md, design.md, tasks.md). Do NOT modify any source code. Do NOT proceed to implementation. After artifacts are generated, STOP and inform the user: "Plan complete. Run `/ccg:spec-impl` to start implementation."
 
 **Steps**
 1. **Select Change**
@@ -84,7 +87,7 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
    - **Bounds**: Value ranges, size limits, rate constraints
 
 5. **Update OPSX Artifacts**
-   - **BEFORE calling `/opsx:continue`**, output a structured summary for OPSX context:
+   - **BEFORE calling `/opsx:continue`** (internal skill call — do NOT expose this command to user), output a structured summary for OPSX context:
      ```markdown
      ## Planning Summary for OPSX
 
@@ -106,11 +109,15 @@ description: '多模型分析 → 消除歧义 → 零决策可执行计划'
      - [High-level task breakdown ready for tasks.md]
      ```
 
-   - Then call `/opsx:continue` to generate next artifacts:
+   - Then call `/opsx:continue` internally to generate next artifacts:
      ```
      /opsx:continue
      ```
    - The OPSX skill will use the above summary to create specs.md, design.md, and tasks.md.
+   - **Note**: This is an internal call. If this step fails, guide the user to re-run `/ccg:spec-plan`.
+   - **STOP**: After artifacts are generated, verify they exist and inform user:
+     "Plan phase complete. Artifacts generated: specs.md, design.md, tasks.md. Run `/ccg:spec-impl` to start implementation."
+     Do NOT proceed to modify source code.
 
 6. **Context Checkpoint**
    - Report current context usage.

package/templates/commands/spec-research.md

@@ -15,6 +15,8 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
 - Each subagent context must be self-contained with independent output.
 - Use `{{MCP_SEARCH_TOOL}}` to minimize grep/find operations.
 - Do not make architectural decisions—surface constraints that guide decisions.
+- **USER GUIDANCE RULE**: When suggesting next steps to the user, ALWAYS use CCG commands (`/ccg:spec-research`, `/ccg:spec-plan`, `/ccg:spec-impl`, `/ccg:spec-review`). NEVER suggest `/opsx:*` commands to the user. If OpenSpec CLI returns error messages referencing OPSX skills, translate them to CCG equivalents.
+- **PHASE BOUNDARY**: This phase ONLY generates the OPSX proposal artifact. Do NOT modify any source code. Do NOT proceed to planning or implementation. After the proposal is generated, STOP and inform the user: "Research complete. Run `/ccg:spec-plan` to continue."
 
 **Steps**
 0. **MANDATORY: Enhance Requirement FIRST**
@@ -110,7 +112,7 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
    - Capture responses as additional constraints.
 
 7. **Finalize OPSX Proposal**
-   - **BEFORE calling `/opsx:continue`**, output a structured summary for OPSX context:
+   - **BEFORE calling `/opsx:continue`** (internal skill call — do NOT expose this command to user), output a structured summary for OPSX context:
      ```markdown
      ## Research Summary for OPSX
 
@@ -130,11 +132,15 @@ description: '需求 → 约束集（并行探索 + OPSX 提案）'
      - [List all user decisions from Step 6]
      ```
 
-   - Then call `/opsx:continue` to generate proposal artifact:
+   - Then call `/opsx:continue` internally to generate proposal artifact:
      ```
      /opsx:continue
      ```
    - The OPSX skill will use the above summary to write proposal.md.
+   - **Note**: This is an internal call. If this step fails, guide the user to re-run `/ccg:spec-research`.
+   - **STOP**: After proposal is generated, verify it exists and inform user:
+     "Research phase complete. Proposal generated. Run `/ccg:spec-plan` to continue planning."
+     Do NOT proceed to planning or implementation.
 
 8. **Context Checkpoint**
    - Report current context usage.