33ea22f259
- 新增 Excel 輸入模組：解析 .xlsx 格式講稿檔案 - 新增 TTS 引擎模組：整合 edge-tts 調用 Azure Neural Voice - 新增 PyQt6 圖形介面：檔案選擇、語音選擇、進度監控 - 新增執行緒模型：QThread + Asyncio 確保 UI 響應性 - 支援 10 種 Neural Voice (中文/越南/英文) - 支援中英混雜、越英混雜發音 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
28 lines
2.0 KiB
Markdown
28 lines
2.0 KiB
Markdown
---
|
|
name: OpenSpec: Archive
|
|
description: Archive a deployed OpenSpec change and update specs.
|
|
category: OpenSpec
|
|
tags: [openspec, archive]
|
|
---
|
|
<!-- OPENSPEC:START -->
|
|
**Guardrails**
|
|
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
|
|
- Keep changes tightly scoped to the requested outcome.
|
|
- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
|
|
|
|
**Steps**
|
|
1. Determine the change ID to archive:
|
|
- If this prompt already includes a specific change ID (for example inside a `<ChangeId>` block populated by slash-command arguments), use that value after trimming whitespace.
|
|
- If the conversation references a change loosely (for example by title or summary), run `openspec list` to surface likely IDs, share the relevant candidates, and confirm which one the user intends.
|
|
- Otherwise, review the conversation, run `openspec list`, and ask the user which change to archive; wait for a confirmed change ID before proceeding.
|
|
- If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
|
|
2. Validate the change ID by running `openspec list` (or `openspec show <id>`) and stop if the change is missing, already archived, or otherwise not ready to archive.
|
|
3. Run `openspec archive <id> --yes` so the CLI moves the change and applies spec updates without prompts (use `--skip-specs` only for tooling-only work).
|
|
4. Review the command output to confirm the target specs were updated and the change landed in `changes/archive/`.
|
|
5. Validate with `openspec validate --strict` and inspect with `openspec show <id>` if anything looks off.
|
|
|
|
**Reference**
|
|
- Use `openspec list` to confirm change IDs before archiving.
|
|
- Inspect refreshed specs with `openspec list --specs` and address any validation issues before handing off.
|
|
<!-- OPENSPEC:END -->
|