AGENT SKILL

archive

Archive the completed change: task gate, delta sync into main specs, revalidate

01 前言 Front Matter

name: archive
description: Archive the completed change: task gate, delta sync into main specs, revalidate
argument-hint: [change-id]

Archiving syncs the deltas into the main specs and freezes the change directory under openspec/changes/archive/.

Check the active changes and their task counts:
```
"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec list --json
```
If no change is active, say so and stop. A change with no tasks (no-tasks) or unfinished tasks fails the archive. The CLI does not block this; the gate is enforced here. Fill missing tasks through tx:plan, unfinished ones through tx:apply.

Archive:

"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec archive <change-id> --yes

Revalidate the synced state. A failure is a defect in the spec state archive produced: fix it and revalidate. A finding against a still-active change belongs to that change, not to this archive:
```
"${CLAUDE_PLUGIN_ROOT}/bin/tx-hook" openspec validate --all --strict --no-interactive --json
```

Plan the change as OpenSpec artifacts: proposal, delta specs, design, tasks

Open a transaction: cut a tx-* branch off base, seed the repo, and route the change

resume the paused git-sync guard

pause the git-sync guard (resume with /tx:git-sync-on)

Close the transaction: archive, docs gate, then squash merge into base after CI passes

Implement the planned change task by task, then judge it