What if I omit the change name?

The skill prompts you to select an active change from openspec list --json and shows only non-archived changes (with any available schema).

What happens if some artifacts or tasks are not done?

The skill warns you about incomplete items and asks for confirmation to proceed; archiving can still occur after your confirmation.

What is delta spec sync and when is it run?

If delta specs exist, the skill performs a sync assessment and may invoke the openspec-sync-specs skill. You can choose to sync now or archive; if you choose to sync, the sync runs and archiving proceeds.

openspec-archive-change

Scanned

npx machina-cli add skill azzgo/agent-skills/openspec-archive-change --openclaw

Files (1)

SKILL.md

4.0 KB

Archive a completed change in the experimental workflow.

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, execute /opsx-sync logic (use the openspec-sync-specs skill). 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

Source

git clone https://github.com/azzgo/agent-skills/blob/main/.opencode/skills/openspec-archive-change/SKILL.mdView on GitHub

Overview

Archive a completed change in the experimental workflow and preserve its history. The skill verifies that all artifacts are done, checks for any incomplete tasks, and optionally syncs delta specs before moving the change into openspec/changes/archive.

How This Skill Works

Using the openspec CLI, it first prompts you to select an active change if none is provided. It then checks artifact completion with openspec status --change "<name>" --json, reads tasks.md for completion, and compares delta specs, potentially invoking the openspec-sync-specs skill. Finally it creates the archive directory, moves the change, preserves .openspec.yaml, and returns a summary.

When to Use It

You have completed implementation of a change in the experimental workflow and want to finalize it.
All artifacts are done and you need to consolidate work by archiving.
You want to review and archive a change after successful testing or validation.
You are closing an active change to reduce clutter while keeping history intact.
A delta-spec exists and you want to assess syncing before archiving (with optional sync).

Quick Start

Step 1: Provide a change name or let the tool prompt you to select an active change.
Step 2: The tool validates artifacts, tasks, and delta specs (and can trigger a sync).
Step 3: Confirm the archive; the change is moved to openspec/changes/archive/YYYY-MM-DD-<name> and a summary is shown.

Best Practices

Always prompt for change selection if the name isn’t provided, don’t guess.
Verify all artifacts are done with openspec status --json before archiving.
Check tasks.md for incomplete tasks and confirm willingness to proceed.
Assess any delta specs against main specs and decide about syncing before archiving.
Archive to openspec/changes/archive/YYYY-MM-DD-<name> and preserve the .openspec.yaml with the directory.

Example Use Cases

Archiving a completed UI change after visual QA passes.
Closing a finished API contract change once integration is green.
Archiving a backend refactor change that passed tests and reviews.
Archiving multiple active changes in a single sprint for cleanup.
Archiving a change when delta specs exist but are already in sync.

Frequently Asked Questions

Add this skill to your agents