xhs_factory/opsx-ff.prompt.md at d88b4e9a3b36616ec65e5a198c7bbcb03272af48

zhoujie 4cde2f7c67 ✨ feat(config): 新增全局设置自动保存功能

- 新增图片生成参数自动保存【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显示
- 显示图片文件大小和状态信息

2026-02-24 21:04:33 +08:00

3.8 KiB

Raw Blame History

description

description
Create a change and generate all artifacts needed for implementation in one go

Fast-forward through artifact creation - generate everything needed to start implementation.

Input: The argument after /opsx:ff 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.
Create the change directory
```
openspec new change "<name>"
```
This creates a scaffolded change at openspec/changes/<name>/.
Get the artifact build order
```
openspec status --change "<name>" --json
```
Parse the JSON to get:
- applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
- artifacts: list of all artifacts with their status and dependencies
Create artifacts in sequence until apply-ready

Use the TodoWrite tool to track progress through the artifacts.

Loop through artifacts in dependency order (artifacts with no pending dependencies first):

a. For each artifact that is ready (dependencies satisfied):
- Get instructions:
```
openspec instructions <artifact-id> --change "<name>" --json
```
- The instructions JSON includes:
  - context: Project background (constraints for you - do NOT include in output)
  - rules: Artifact-specific rules (constraints for you - do NOT include in output)
  - template: The structure to use for your output file
  - instruction: Schema-specific guidance for this artifact type
  - outputPath: Where to write the artifact
  - dependencies: Completed artifacts to read for context
- Read any completed dependency files for context
- Create the artifact file using template as the structure
- Apply context and rules as constraints - but do NOT copy them into the file
- Show brief progress: "✓ Created "
b. Continue until all applyRequires artifacts are complete
- After creating each artifact, re-run openspec status --change "<name>" --json
- Check if every artifact ID in applyRequires has status: "done" in the artifacts array
- Stop when all applyRequires artifacts are done
c. If an artifact requires user input (unclear context):
- Use AskUserQuestion tool to clarify
- Then continue with creation
Show final status
```
openspec status --change "<name>"
```

Output

After completing all artifacts, summarize:

Change name and location
List of artifacts created with brief descriptions
What's ready: "All artifacts created! Ready for implementation."
Prompt: "Run /opsx:apply to start implementing."

Artifact Creation Guidelines

Follow the instruction field from openspec instructions for each artifact type
The schema defines what each artifact should contain - follow it
Read dependency artifacts for context before creating new ones
Use the template as a starting point, filling in based on context

Guardrails

Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
Always read dependency artifacts before creating a new one
If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
If a change with that name already exists, ask if user wants to continue it or create a new one
Verify each artifact file exists after writing before proceeding to next

3.8 KiB Raw Blame History

3.8 KiB

Raw Blame History