xhs_factory/opsx-archive.prompt.md at 4d83c0f4a950b3b85bfe9bdb48008d6d3bd395e8

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

4.6 KiB

Raw Blame History

description

description
Archive a completed change in the experimental workflow

Archive a completed change in the experimental workflow.

Input: Optionally specify a change name after /opsx:archive (e.g., /opsx:archive add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

If no change name provided, prompt for selection

Run openspec list --json to get available changes. Use the AskUserQuestion tool to let the user select.

Show only active changes (not already archived). Include the schema used for each change if available.

IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Check artifact completion status

Run openspec status --change "<name>" --json to check artifact completion.

Parse the JSON to understand:
- schemaName: The workflow being used
- artifacts: List of artifacts with their status (done or other)
If any artifacts are not done:
- Display warning listing incomplete artifacts
- Prompt user for confirmation to continue
- Proceed if user confirms
Check task completion status

Read the tasks file (typically tasks.md) to check for incomplete tasks.

Count tasks marked with - [ ] (incomplete) vs - [x] (complete).

If incomplete tasks found:
- Display warning showing count of incomplete tasks
- Prompt user for confirmation to continue
- Proceed if user confirms
If no tasks file exists: Proceed without task-related warning.
Assess delta spec sync state

Check for delta specs at openspec/changes/<name>/specs/. If none exist, proceed without sync prompt.

If delta specs exist:
- Compare each delta spec with its corresponding main spec at openspec/specs/<capability>/spec.md
- Determine what changes would be applied (adds, modifications, removals, renames)
- Show a combined summary before prompting
Prompt options:
- If changes needed: "Sync now (recommended)", "Archive without syncing"
- If already synced: "Archive now", "Sync anyway", "Cancel"
If user chooses sync, execute /opsx:sync logic. Proceed to archive regardless of choice.
Perform the archive

Create the archive directory if it doesn't exist:
```
mkdir -p openspec/changes/archive
```
Generate target name using current date: YYYY-MM-DD-<change-name>

Check if target already exists:
- If yes: Fail with error, suggest renaming existing archive or using different date
- If no: Move the change directory to archive
```
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
```
Display summary

Show archive completion summary including:
- Change name
- Schema that was used
- Archive location
- Spec sync status (synced / sync skipped / no delta specs)
- Note about any warnings (incomplete artifacts/tasks)

Output On Success

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** ✓ Synced to main specs

All artifacts complete. All tasks complete.

Output On Success (No Delta Specs)

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** No delta specs

All artifacts complete. All tasks complete.

Output On Success With Warnings

## Archive Complete (with warnings)

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** Sync skipped (user chose to skip)

**Warnings:**
- Archived with 2 incomplete artifacts
- Archived with 3 incomplete tasks
- Delta spec sync was skipped (user chose to skip)

Review the archive if this was not intentional.

Output On Error (Archive Exists)

## Archive Failed

**Change:** <change-name>
**Target:** openspec/changes/archive/YYYY-MM-DD-<name>/

Target archive directory already exists.

**Options:**
1. Rename the existing archive
2. Delete the existing archive if it's a duplicate
3. Wait until a different date to archive

Guardrails

Always prompt for change selection if not provided
Use artifact graph (openspec status --json) for completion checking
Don't block archive on warnings - just inform and confirm
Preserve .openspec.yaml when moving to archive (it moves with the directory)
Show clear summary of what happened
If sync is requested, use /opsx:sync approach (agent-driven)
If delta specs exist, always run the sync assessment and show the combined summary before prompting

4.6 KiB Raw Blame History

4.6 KiB

Raw Blame History