skills.rest
knopki
knopkiCOMMUNITY
Explore all skills by this author →
𝕏@knopkiGitHub

openspec-archive-change

Archive completed changes after validating artifacts and syncing delta specifications.

1|Updated Jun 18, 2025
Search Tags:#workflow#version control#specifications#archive#change management#openspec
One-click install
npx skills add https://github.com/knopki/dotfiles --skill openspec-archive-change-knopki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/knopki/dotfiles --skill openspec-archive-change-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you finalize and archive completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Archive completed changes: Moves a finalized change to an archive directory.
  • Validate artifact and task completion: Checks if all associated artifacts and tasks are marked as done before archiving.
  • Assess and sync delta specs: Compares local changes with main specifications and offers to sync them before archiving.
  • Use Case: After implementing a new feature and testing all its components, you can use this skill to archive the change, ensuring all related work is properly stored and versioned.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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 changes in an experimental workflow?▼

To archive completed changes, you must first validate that all associated artifacts and tasks are marked as done. This skill then moves the finalized change to an archive directory to maintain a clean project history.

Do I need the openspec CLI to archive change specifications?▼

Yes, you need the openspec CLI installed. The archiving process requires it to perform status checks and list changes before moving the completed workflow to the archive directory.

What happens to delta specifications when I archive a change?▼

When archiving a change, the skill assesses delta specifications against main specifications. It offers to sync these local changes before moving the change to the archive directory.

Can I archive a change if artifact and task completion is not validated?▼

No, archiving requires validating artifact and task completion first. The process checks if all associated artifacts and tasks are marked as done before moving the change to the archive directory.

What is the best way to finalize and organize completed feature changes?▼

The best way to finalize completed feature changes is to use an automated archiving skill. It validates task completion, syncs delta specifications, and moves the change to an archive directory for organized version control.

Related Skills

Explore More Software Engineering Skills→
zhentingWu-wztzhentingWu-wzt
6

openspec-archive-change

Archive completed openspec experimental changes after validating artifact status and task completion.

Community
Advanced
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

Official
Advanced
yuboonyuboon
5

openspec-archive-change

Archive completed changes after verifying artifacts and syncing delta specifications.

Community
Advanced
daodaoedudaodaoedu

openspec-archive-change

Archive completed OpenSpec change directories after validating artifacts and tasks.

Official
Advanced