ssd-ql-workflow 0.1.0

package/README.md

@@ -0,0 +1,116 @@
+# @ql/sdd-cli
+
+SDD (Skill-Driven Development) CLI Tool - 一键初始化 Trinity Workflow 配置。
+
+## 安装
+
+```bash
+# 使用 npx（推荐）
+npx @ql/sdd-cli init
+
+# 或全局安装
+npm install -g @ql/sdd-cli
+sdd-cli init
+```
+
+## 快速开始
+
+```bash
+# 在项目根目录执行
+npx @ql/sdd-cli init
+
+# 初始化成功后，可用的命令：
+# /sdd-new <change-name>  - 创建新的 SDD workflow
+# /sdd-continue           - 继续下一个 artifact
+# /sdd-apply              - 执行任务
+# /sdd-status             - 查看状态
+```
+
+## 命令
+
+### `init`
+
+初始化 SDD workflow 配置：
+
+```bash
+npx @ql/sdd-cli init [options]
+
+Options:
+  -f, --force       覆盖已存在的文件
+  --no-commands     跳过命令文件复制
+  --no-schema       跳过 schema 文件复制
+```
+
+### `list`
+
+列出可用的命令和 schema：
+
+```bash
+npx @ql/sdd-cli list
+```
+
+## 生成的文件结构
+
+```
+your-project/
+├── openspec/
+│   ├── config.yaml                      # OpenSpec 配置
+│   ├── project.md                       # 项目说明
+│   ├── .active                          # 活动状态文件
+│   ├── schemas/
+│   │   └── trinity-workflow/
+│   │       └── schema.yaml              # 三位一体架构 schema
+│   ├── specs/                           # 规格文档目录
+│   └── changes/                         # 变更目录
+└── .opencode/
+    └── commands/
+        ├── sdd-new.md                   # SDD 新建命令
+        ├── sdd-continue.md              # SDD 继续命令
+        ├── sdd-apply.md                 # SDD 执行命令
+        ├── sdd-status.md                # SDD 状态命令
+        └── opsx-*.md                    # OPSX 原生命令
+```
+
+## Trinity Workflow 架构
+
+三位一体架构整合了：
+
+1. **追踪层** (Planning-with-Files)
+   - `task_plan.md` - 阶段、目标、决策
+   - `findings.md` - 技术发现、架构决策
+   - `progress.md` - 会话进度日志
+
+2. **方法层** (阶段式产出)
+   - `proposal.md` - 需求探索
+   - `design.md` - 技术设计
+   - `specs/` - 功能规格
+   - `tasks.md` - 任务分解
+
+3. **执行层** (3-Strike 协议)
+   - Attempt 1: 诊断并修复
+   - Attempt 2: 尝试替代方案
+   - Attempt 3: 重新思考问题
+
+## SDD vs OPSX 命令对照
+
+| SDD Command | OPSX Equivalent | 说明 |
+|-------------|-----------------|------|
+| `/sdd-new` | `/opsx-new --schema trinity-workflow` | 创建 change |
+| `/sdd-continue` | `/opsx-continue` | 继续 artifact |
+| `/sdd-apply` | `/opsx-apply` | 执行任务 |
+| `/sdd-status` | `/opsx-status` | 查看状态 |
+
+## 开发
+
+```bash
+# 安装依赖
+cd packages/sdd-cli
+npm install
+
+# 本地测试
+node bin/cli.js init
+```
+
+## License
+
+MIT

package/bin/cli.js

@@ -0,0 +1,126 @@
+#!/usr/bin/env node
+
+import { program } from 'commander';
+import fs from 'fs-extra';
+import path from 'path';
+import { fileURLToPath } from 'url';
+import chalk from 'chalk';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+const TEMPLATES_DIR = path.join(__dirname, '..', 'templates');
+
+program
+  .name('sdd-cli')
+  .description('SDD (Skill-Driven Development) CLI Tool')
+  .version('0.1.0');
+
+program
+  .command('init')
+  .description('Initialize SDD workflow configuration in current project')
+  .option('-f, --force', 'Overwrite existing files', false)
+  .option('--no-commands', 'Skip copying command files', false)
+  .option('--no-schema', 'Skip copying schema files', false)
+  .action(async (options) => {
+    const cwd = process.cwd();
+    console.log(chalk.blue('\n🚀 Initializing SDD workflow...\n'));
+
+    try {
+      // 1. Copy openspec config and schema
+      if (options.schema !== false) {
+        const openspecDir = path.join(cwd, 'openspec');
+
+        // Create openspec directory structure
+        await fs.ensureDir(path.join(openspecDir, 'schemas', 'trinity-workflow'));
+        await fs.ensureDir(path.join(openspecDir, 'specs'));
+        await fs.ensureDir(path.join(openspecDir, 'changes'));
+
+        // Copy config.yaml
+        const configSrc = path.join(TEMPLATES_DIR, 'openspec', 'config.yaml');
+        const configDest = path.join(openspecDir, 'config.yaml');
+
+        if (await fs.exists(configDest) && !options.force) {
+          console.log(chalk.yellow('⚠ config.yaml already exists, use --force to overwrite'));
+        } else {
+          await fs.copy(configSrc, configDest);
+          console.log(chalk.green('✓ Created openspec/config.yaml'));
+        }
+
+        // Copy trinity-workflow schema
+        const schemaSrc = path.join(TEMPLATES_DIR, 'openspec', 'schemas', 'trinity-workflow', 'schema.yaml');
+        const schemaDest = path.join(openspecDir, 'schemas', 'trinity-workflow', 'schema.yaml');
+
+        if (await fs.exists(schemaDest) && !options.force) {
+          console.log(chalk.yellow('⚠ trinity-workflow/schema.yaml already exists, use --force to overwrite'));
+        } else {
+          await fs.copy(schemaSrc, schemaDest);
+          console.log(chalk.green('✓ Created openspec/schemas/trinity-workflow/schema.yaml'));
+        }
+
+        // Create project.md template if not exists
+        const projectMdPath = path.join(openspecDir, 'project.md');
+        if (!await fs.exists(projectMdPath)) {
+          await fs.writeFile(projectMdPath, `# Project Overview\n\nDescribe your project here.\n`, 'utf8');
+          console.log(chalk.green('✓ Created openspec/project.md'));
+        }
+
+        // Create .active file
+        const activeFile = path.join(openspecDir, '.active');
+        if (!await fs.exists(activeFile)) {
+          await fs.writeFile(activeFile, '');
+        }
+      }
+
+      // 2. Copy opencode commands
+      if (options.commands !== false) {
+        const commandsDir = path.join(cwd, '.opencode', 'commands');
+        await fs.ensureDir(commandsDir);
+
+        const templateCommandsDir = path.join(TEMPLATES_DIR, 'opencode', 'commands');
+        const commands = await fs.readdir(templateCommandsDir);
+
+        let copiedCount = 0;
+        for (const cmd of commands) {
+          if (cmd.endsWith('.md')) {
+            const src = path.join(templateCommandsDir, cmd);
+            const dest = path.join(commandsDir, cmd);
+
+            if (await fs.exists(dest) && !options.force) {
+              console.log(chalk.gray(`  ${cmd} already exists, skipping`));
+            } else {
+              await fs.copy(src, dest);
+              copiedCount++;
+            }
+          }
+        }
+        console.log(chalk.green(`✓ Copied ${copiedCount} command files to .opencode/commands/`));
+      }
+
+      console.log('\n' + chalk.green.bold('✅ SDD workflow initialized successfully!'));
+      console.log('\n📚 Next steps:');
+      console.log(chalk.cyan('   /sdd-new <change-name>') + '   - Start a new SDD workflow');
+      console.log(chalk.cyan('   /sdd-continue') + '         - Continue to next artifact');
+      console.log(chalk.cyan('   /sdd-apply') + '            - Execute tasks');
+      console.log(chalk.cyan('   /sdd-status') + '           - View workflow status\n');
+
+    } catch (error) {
+      console.error(chalk.red('\n❌ Initialization failed:'), error.message);
+      process.exit(1);
+    }
+  });
+
+program
+  .command('list')
+  .description('List available commands and schemas')
+  .action(() => {
+    console.log(chalk.bold('\n📚 Available SDD Commands:'));
+    console.log('   /sdd-new       - Start a new SDD workflow');
+    console.log('   /sdd-continue  - Continue to next artifact');
+    console.log('   /sdd-apply     - Execute tasks from workflow');
+    console.log('   /sdd-status    - View workflow status');
+
+    console.log(chalk.bold('\n📦 Available Schemas:'));
+    console.log('   trinity-workflow - 三位一体架构工作流\n');
+  });
+
+program.parse();

package/package.json

@@ -0,0 +1,37 @@
+{
+  "name": "ssd-ql-workflow",
+  "version": "0.1.0",
+  "description": "SDD (Skill-Driven Development) CLI - Initialize trinity-workflow schema and commands",
+  "type": "module",
+  "bin": {
+    "sdd": "./bin/cli.js"
+  },
+  "files": [
+    "bin",
+    "templates"
+  ],
+  "keywords": [
+    "sdd",
+    "openspec",
+    "workflow",
+    "cli",
+    "trinity",
+    "claude",
+    "opencode"
+  ],
+  "author": "ql",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ql-wade/sdd-cli"
+  },
+  "dependencies": {
+    "chalk": "^5.3.0",
+    "commander": "^12.0.0",
+    "fs-extra": "^11.2.0",
+    "ora": "^8.0.0"
+  }
+}

package/templates/opencode/commands/opsx-apply.md

@@ -0,0 +1,149 @@
+---
+description: Implement tasks from an OpenSpec change (Experimental)
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name (e.g., `/opsx-apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/opsx-apply <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   openspec instructions apply --change "<name>" --json
+   ```
+
+   This returns:
+   - Context file paths (varies by schema)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx-continue`
+   - If `state: "all_done"`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+   Read the files listed in `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! You can archive this change with `/opsx-archive`.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/templates/opencode/commands/opsx-archive.md

@@ -0,0 +1,154 @@
+---
+description: Archive a completed change in the experimental workflow
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name after `/opsx-archive` (e.g., `/opsx-archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run `openspec status --change "<name>" --json` to check artifact completion.
+
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used
+   - `artifacts`: List of artifacts with their status (`done` or other)
+
+   **If any artifacts are not `done`:**
+   - Display warning listing incomplete artifacts
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Prompt user for confirmation to continue
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create the archive directory if it doesn't exist:
+   ```bash
+   mkdir -p openspec/changes/archive
+   ```
+
+   Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move the change directory to archive
+
+   ```bash
+   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Spec sync status (synced / sync skipped / no delta specs)
+   - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success (No Delta Specs)**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** No delta specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success With Warnings**
+
+```
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** Sync skipped (user chose to skip)
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped (user chose to skip)
+
+Review the archive if this was not intentional.
+```
+
+**Output On Error (Archive Exists)**
+
+```
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+```
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use the Skill tool to invoke `openspec-sync-specs` (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting