quyixiao/eb-service-api
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
eb-service-api/.claude/commands/opsx/new.md
zhengli 08b029dfa5 docs(project): 添加项目文档和工作流命令定义 
- 新增 CLAUDE.md 文件，提供项目概述、技术栈、构建命令、模块结构等详细指导
- 新增 opsx 工作流相关命令定义文件，包括 apply、archive、bulk-archive、continue、explore 等
- 配置 OpenSpec 规范，设置为 spec-driven 模式
- 定义实验性工作流命令，支持变更应用、归档、继续开发等功能
- 添加探索模式命令，用于深入思考和代码库调研
2026-05-25 17:58:13 +08:00

2.6 KiB
Raw Blame History

name description category tags
OPSX: New Start a new change using the experimental artifact workflow (OPSX) Workflow
workflow
artifacts
experimental

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

  1. 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.

  2. 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.

  3. 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.

  4. Show the artifact status

    openspec status --change "<name>"

    This shows which artifacts need to be created and which are ready (dependencies satisfied).

  5. 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.

  6. 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