skills.rest
nfelix25
nfelix25COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed changes after verifying artifacts, tasks, and delta spec sync.

Updated Mar 3, 2026
Search Tags:#workflow#specification#CLI#archive#change management
One-click install
npx skills add https://github.com/nfelix25/home-movies --skill openspec-archive-change-nfelix25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/nfelix25/home-movies/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/nfelix25/home-movies --skill openspec-archive-change-nfelix25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes in an experimental workflow, ensuring that changes are finalized and stored securely for future reference.

Core Features & Use Cases

  • Change Archival: Archive completed changes to maintain a historical record of the experimental workflow.
  • Input Handling: Allows specification of a change name or automatic inference from context.
  • Completion Verification: Checks for artifact and task completion before archiving.
  • Spec Sync Assessment: Assesses delta spec sync state for integrity before archiving.
  • Archive Execution: Performs the actual archiving process with a summary display.

Quick Start

Archive the completed change named 'feature-123' using the openspec-archive-change skill.

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 workflow changes using a CLI?▼

To archive completed workflow changes, this Skill automates the process by verifying all artifacts and tasks are complete before moving them to the archive. It uses the openspec CLI to execute the archival and display a summary.

What happens if my delta spec is not synced before archiving a change?▼

Before archiving a change, the Skill assesses your delta spec sync state to ensure data integrity. If artifacts or tasks are incomplete, it blocks the archival process and prompts for user confirmation.

Do I need the openspec CLI to finalize and archive experimental changes?▼

Yes, the openspec CLI is a required dependency for change management. You need it installed to automate the archival process, verify completion, and check delta spec sync states.

Can I archive a change without specifying its name explicitly?▼

Yes, the Skill allows you to specify a change name manually or automatically infers the target change from the current context. It then verifies completion before executing the archival process.

When should I archive completed changes in a specification workflow?▼

You should archive completed changes once all associated artifacts and tasks are finalized. Archiving maintains a secure historical record of the experimental workflow for future reference.

Related Skills

Explore More Software Engineering Skills→
sundaiclawsundaiclaw
7

openspec-archive-change

Archive completed OpenSpec changes with artifact and delta-spec checks.

Community
Advanced
Sharper-FlowSharper-Flow
4

adv-reflect

Analyze archived engineering change data to generate structured postmortem reports.

Official
Advanced
lz-freedomlz-freedom

openspec-archive-change

Archive validated openspec changes into dated archive folders with metadata.

Community
Advanced
darblexdarblex

git-essentials

Provide essential Git commands for version control, branching, and collaboration.

Community
Intermediate