zhoujie
4cde2f7c67
- 新增图片生成参数自动保存【quality_mode、sd_steps、sd_cfg_scale、sd_negative_prompt】 - 新增自动运营调度参数自动保存【sched_comment_on、sched_like_on、sched_fav_on、sched_reply_on、sched_publish_on】 - 新增智能学习参数自动保存【learn_interval】 - 新增内容排期参数自动保存【queue_gen_count】 - 优化人设切换逻辑，同时保存到配置并更新队列主题池 - 新增页面加载时自动恢复全局设置功能 📝 docs(config): 更新配置管理文档 - 在config_manager.py中新增默认配置项 - 在main.py中实现启动时自动加载全局设置 - 更新配置保存测试脚本_test_config_save.py 📦 build(ui): 优化用户界面交互 - 图片生成参数变更时自动保存到配置 - 自动运营参数变更时自动保存到配置 - 智能学习参数变更时自动保存到配置 - 内容排期参数变更时自动保存到配置 - 修复人设切换时队列主题池未更新的问题 🐛 fix(queue): 修复发布队列图片显示问题 - 在publish_queue.py中新增图片预览功能 - 支持将图片转换为base64编码嵌入markdown显示 - 显示图片文件大小和状态信息
67 lines
2.5 KiB
Markdown
67 lines
2.5 KiB
Markdown
---
|
|
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**
|
|
|
|
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**
|
|
```bash
|
|
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**
|
|
```bash
|
|
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".
|
|
```bash
|
|
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
|