skills.rest
lewisoepwqi
lewisoepwqiCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

2|Updated Jan 29, 2026
Search Tags:#workflow#sync#archive#openspec#artifact#changes#task
One-click install
npx skills add https://github.com/lewisoepwqi/scientific_nini --skill openspec-archive-change-lewisoepwqi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/lewisoepwqi/scientific_nini/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/lewisoepwqi/scientific_nini --skill openspec-archive-change-lewisoepwqi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change after implementation to close the loop and maintain a clean repository of changes.

Core Features & Use Cases

  • Prompt for the change name and verify status of artifacts and tasks.
  • Check artifact completion via openspec status and assess delta spec synchronization needs.
  • Archive the change by moving the directory to openspec/changes/archive/YYYY-MM-DD-<name>, preserving .openspec.yaml and providing a clear summary.

Quick Start

Archive a completed OpenSpec change by selecting the change, validating artifacts and tasks, syncing delta specs when applicable, and moving the change into the archive directory.

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 after implementation?▼

To archive completed OpenSpec changes, the workflow validates artifact and task completion via openspec status, syncs delta specs if needed, and safely moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name>.

What happens to OpenSpec artifacts and tasks during the archival process?▼

During OpenSpec archival, the system checks artifact completion and task status using the OpenSpec CLI, prompting the user to ensure all delta specs are synchronized before the change is moved to the archive directory.

Do I need the OpenSpec CLI to finalize and sync delta specs for a change?▼

Yes, the OpenSpec CLI is required to orchestrate status checks, verify artifact completion, assess delta spec synchronization needs, and execute the safe archival moves with proper logging.

When should I archive an OpenSpec change in the workflow?▼

You should archive an OpenSpec change when finalizing implementations, ensuring all artifacts and tasks are complete and delta specs are synced, to close the loop and maintain a clean repository of changes.

Does archiving an OpenSpec change preserve the configuration file?▼

Yes, archiving an OpenSpec change preserves the .openspec.yaml configuration file while moving the directory to openspec/changes/archive/YYYY-MM-DD-<name> and providing a clear summary of the archival.

Related Skills

Explore More Software Engineering Skills→
whatevertogowhatevertogo

openspec-archive-change

Archive completed openspec changes after validating artifacts and delta specs.

Community
Advanced
Alex1980AlexAlex1980Alex

openspec-archive-change

Archive completed OpenSpec changes into dated directories after completion checks.

Community
Advanced
epamepam
503

openspec-archive-change

Validate and archive completed Openspec workflow changes while preserving configuration files.

Official
Advanced
brainsnorkelbrainsnorkel

openspec-archive-change

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

Community
Advanced