skills.rest
alexzhang1030
alexzhang1030COMMUNITY
Explore all skills by this author →
𝕏@alexz_devGitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated Mar 17, 2026
Search Tags:#workflow#cli#artifacts#archive#openspec#spec-sync
One-click install
npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-archive-change-alexzhang1030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/alexzhang1030/platform-demo/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-archive-change-alexzhang1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual friction of finalizing a completed OpenSpec change by checking readiness, handling user confirmation, and moving the change into the archive in a controlled way.

Core Features & Use Cases

  • Change Selection: Helps users choose the correct active change when no name is provided or the request is ambiguous.
  • Completion Validation: Verifies artifact status and task completion before archiving so incomplete work is clearly surfaced.
  • Spec Sync Assessment: Compares delta specs against main specs and supports syncing before archive when needed.
  • Archive Execution: Safely moves the change into a dated archive path and reports the outcome.
  • Use Case: A developer finishes an experimental workflow change, confirms all tasks are done, optionally syncs specs, and archives the work with a clear summary.

Quick Start

Use this skill to archive the completed OpenSpec change named my-change after confirming its artifacts, tasks, and spec sync status.

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 a completed OpenSpec change safely?▼

To archive a completed OpenSpec change safely, the system verifies artifact status, checks task completion, assesses delta spec sync, and moves the directory to a dated archive path after guarded user confirmation.

When should I sync delta specs before archiving an OpenSpec change?▼

Sync delta specs before archiving an OpenSpec change when differences exist between delta and main specs, allowing you to synchronize changes before the final directory move into the archive.

Does archiving an OpenSpec change require the openspec CLI?▼

Yes, archiving an OpenSpec change requires the openspec CLI to perform status checks, validate archive paths, and execute the directory moving process.

What happens if I try to archive an incomplete OpenSpec change?▼

If you try to archive an incomplete OpenSpec change, the completion validation process surfaces incomplete work by verifying artifact status and task completion before allowing the archive execution to proceed.

Can I select which active OpenSpec change to archive if I have multiple?▼

Yes, you can select which active OpenSpec change to archive, as the system helps you choose the correct active change when no name is provided or the request is ambiguous.

Related Skills

Explore More Software Engineering Skills→
Myriad-DreaminMyriad-Dreamin
3.5k

openspec-archive-change

Archive completed changes in the experimental workflow using the openspec CLI.

Community
Intermediate
ondataondata
9

openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes with conflict resolution and dated paths.

Official
Advanced
ConductionNLConductionNL

openspec-archive-change

Validate artifacts and tasks before archiving completed OpenSpec changes.

Official
Advanced
jankneumannjankneumann
4

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

Community
Advanced