skills.rest
OiAnthony
OiAnthonyCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating task and artifact completion.

8|Updated Jan 19, 2026
Search Tags:#workflow#validation#cli#archiving#openspec#spec-sync
One-click install
npx skills add https://github.com/OiAnthony/.agents --skill openspec-archive-change-oianthony
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/OiAnthony/.agents/tree/main/skills/openspec-archive-change
Command: npx skills add https://github.com/OiAnthony/.agents --skill openspec-archive-change-oianthony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finalizes completed OpenSpec work by safely archiving a change only after it has been reviewed for completion, reducing the risk of closing out unfinished or unsynced work.

Core Features & Use Cases

  • Change Selection: Helps identify the exact change to archive when the user does not provide a clear name.
  • Completion Checks: Verifies artifact status, incomplete tasks, and delta spec sync state before archiving.
  • Safe Archiving: Moves the change into a date-stamped archive folder and preserves the workflow metadata.
  • Use Case: A developer finishes implementation and asks the Skill to archive the change, confirm whether any tasks remain open, and decide whether specs should be synced first.

Quick Start

Ask the AI to archive the completed OpenSpec change by name and confirm any incomplete artifacts, tasks, or spec sync steps before finalizing it.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed OpenSpec changes safely?▼

You can archive completed OpenSpec changes by selecting the change, checking artifact and task completion, confirming incomplete items, and moving the directory to a date-stamped archive folder using CLI commands.

What does OpenSpec validation check before archiving a change?▼

OpenSpec validation checks artifact status, incomplete tasks, and delta spec sync state before archiving, requiring user confirmation for any incomplete items to prevent closing out unfinished work.

Do I need the openspec CLI to archive changes?▼

Yes, you need the openspec CLI. The workflow relies on its status and list commands to verify completion readiness before executing safe archive directory moves with date-based naming.

Can I archive a change if tasks or artifacts are still incomplete?▼

You can archive a change with incomplete items only after explicit user confirmation, but the workflow is designed to verify artifact status and task completion first to reduce the risk of archiving unfinished work.

When should I sync delta specs before finalizing an OpenSpec archive?▼

You should sync delta specs before finalizing when the validation check identifies unsynced spec changes, allowing you to decide whether to sync first or proceed with user confirmation for incomplete items.

Related Skills

Explore More Software Engineering Skills→
tim-hubtim-hub
2

openspec-verify-change

Verify OpenSpec change implementations against specs, tasks, and design artifacts.

Community
Advanced
tatargabortatargabor
30

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes into a date-stamped directory.

Community
Advanced
zooroyzooroy

spectra-archive

Archive spectra changes after validating artifacts, tasks, and delta spec sync.

Community
Advanced
pabloimrik17pabloimrik17

openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

Community
Advanced