huang
034f00e2e7
- 添加 IoT 核心业务表：运营商、IoT 卡、设备、号卡、套餐、订单等 - 添加分佣系统表：分佣规则、分佣记录、运营商结算等 - 添加轮询和流量管理表：轮询配置、流量使用记录等 - 添加财务和系统管理表：佣金提现、换卡申请等 - 实现完整的 GORM 模型和常量定义 - 添加数据库迁移脚本和详细文档 - 集成 OpenSpec 工作流工具（opsx 命令和 skills） Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2.6 KiB
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.
-
Select a workflow schema
Run
openspec schemas --jsonto get available schemas with descriptions.Use the AskUserQuestion tool to let the user choose a workflow:
- Present each schema with its description
- Mark
spec-drivenas "(default)" if it's available - Example options: "spec-driven - proposal → specs → design → tasks (default)", "tdd - tests → implementation → docs"
If user doesn't have a preference, default to
spec-driven. -
Create the change directory
openspec new change "<name>" --schema "<selected-schema>"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
- Selected schema/workflow 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:continueor 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:continueinstead - Always pass --schema to preserve the user's workflow choice