Openspec Archive Change Skill for Claude

Archive a completed change in the experimental workflow.

> ## ⚠️ 本仓附加：归档门（add-local-prepublish-gate · 2026-07-26 定）

>

> 归档前 MUST 先跑本机归档门，不过就不许 archive：

>

> `bash

> npm run openspec:gate -- <change-name>

> `

>

> 两条判据同时满足才放行：① tasks.md 无未勾条目；② 每个 [真机] 项的「验收日期 / 真机工程」都已填实（空串 / TBD / ____-__-__ 一律判未填）。

>

> 为什么加这道门：复选框作为门控信号在本仓已被证伪——9 个已归档 change 带着未勾任务归档，其中 debrand-rrv-to-mg 是 35 项未勾 / 0 项已勾就归档，而代码早已落地。复选框已无法区分「没做」和「做了没勾」。该门只对从今往后的归档生效，不回溯补勾历史 change。

>

> 门的实现在 openspec/gate.mjs（openspec/ 不入 git，属本机工具，不随 npm 包分发；也不挂在 prepublishOnly 上——发版门与归档门是两件事）。

>

> ⚠️ 本文件是 openspec CLI 生成物（front-matter generatedBy: "1.3.1"），CLI 升级可能覆盖本段；且它有两份镜像（.claude/skills/ 与 .agents/skills/），改一处须同步另一处。升级后请复查本段是否还在。

Input: Optionally specify a change name. 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
• Use AskUserQuestion tool to confirm user wants to proceed
• 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
• Use AskUserQuestion tool to confirm user wants to proceed
• 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, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). 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
• Whether specs were synced (if applicable)
• 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 (or "No delta specs" or "Sync skipped")

All artifacts complete. All tasks complete.

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 openspec-sync-specs approach (agent-driven)
• If delta specs exist, always run the sync assessment and show the combined summary before prompting