junhong_cmp_fiber/.opencode/command/opsx-new.md at b9c3875c08cd086a3e6699285a9260b3a0d150b2

csxj2026/junhong_cmp_fiber

Files

构建并部署到测试环境（无 SSH） / build-and-deploy (push) Successful in 6m33s

Details

**变更说明**:
- 删除所有 *_test.go 文件（单元测试、集成测试、验收测试、流程测试）
- 删除整个 tests/ 目录
- 更新 CLAUDE.md：用"测试禁令"章节替换所有测试要求
- 删除测试生成 Skill (openspec-generate-acceptance-tests)
- 删除测试生成命令 (opsx:gen-tests)
- 更新 tasks.md：删除所有测试相关任务

**新规范**:
- ❌ 禁止编写任何形式的自动化测试
- ❌ 禁止创建 *_test.go 文件
- ❌ 禁止在任务中包含测试相关工作
- ✅ 仅当用户明确要求时才编写测试

**原因**:
业务系统的正确性通过人工验证和生产环境监控保证，测试代码维护成本高于价值。

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2026-02-11 17:13:42 +08:00

2.5 KiB

Raw Blame History

description

description
Start a new change using the experimental artifact workflow (OPSX)

Start a new change using the experimental artifact-driven approach.

Input: The argument after /opsx-new is the change name (kebab-case), OR a description of what the user wants to build.

Steps

If no input provided, ask what they want to build

Use the AskUserQuestion tool (open-ended, no preset options) to ask:

"What change do you want to work on? Describe what you want to build or fix."

From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

IMPORTANT: Do NOT proceed without understanding what the user wants to build.
Determine the workflow schema

Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

Use a different schema only if the user mentions:
- A specific schema name → use --schema <name>
- "show workflows" or "what workflows" → run openspec schemas --json and let them choose
Otherwise: Omit --schema to use the default.
Create the change directory
```
openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
Show the artifact status
```
openspec status --change "<name>"
```
This shows which artifacts need to be created and which are ready (dependencies satisfied).
Get instructions for the first artifact The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
```
openspec instructions <first-artifact-id> --change "<name>"
```
This outputs the template and context for creating the first artifact.
STOP and wait for user direction

Output

After completing the steps, summarize:

Change name and location
Schema/workflow being used and its artifact sequence
Current status (0/N artifacts complete)
The template for the first artifact
Prompt: "Ready to create the first artifact? Run /opsx-continue or just describe what this change is about and I'll draft it."

Guardrails

Do NOT create any artifacts yet - just show the instructions
Do NOT advance beyond showing the first artifact template
If the name is invalid (not kebab-case), ask for a valid name
If a change with that name already exists, suggest using /opsx-continue instead
Pass --schema if using a non-default workflow

2.5 KiB Raw Blame History

2.5 KiB

Raw Blame History