Archive an OpenSpec change after checking its documents, task completion, and specification differences. The skill offers a choice about updating the main specifications, then moves the change into a dated archive and reports the result.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Review the instructions the agent will receive before you install.
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 usedartifacts: List of artifacts with their status (done or other)If any artifacts are not done:
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:
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:
openspec/specs/<capability>/spec.mdPrompt options:
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:
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
Display summary
Show archive completion summary including:
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement pending tasks from an OpenSpec change, a planned set of development work. The skill reads relevant specifications and design files, makes focused code changes, and updates task completion as work progresses.
Archive several OpenSpec changes together after reviewing their documents, task completion, and specification conflicts. The agent checks actual code to decide which specification updates to apply, asks for confirmation, and reports successes, skipped changes, and failures.
Continue an existing OpenSpec change by creating one next document. Check progress and dependencies, follow the workflow's template, and report what was completed and which documents are now available to create.
Explore development ideas and problems through conversation, code investigation, diagrams, and comparisons. The skill helps clarify requirements, weigh approaches, and surface risks before or during a change, with optional documentation of decisions when requested.
Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.
Set up a new OpenSpec change for a feature, fix, or modification. Create its working directory, show the document sequence and current status, and present the first template so drafting can begin.