openspec-archive-change

Archive completed openspec changes with timestamped directories after validation.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-archive-change-agentic-engineering-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-archive-change-agentic-engineering-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the experimental workflow by providing a clear process to finalize and archive completed changes, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to an archive directory with a timestamped name.
  • Validation Checks: Verifies artifact and task completion status before archiving.
  • Spec Synchronization: Assesses and optionally syncs delta specs with main specs.
  • Use Case: After successfully implementing and testing a new feature, use this Skill to archive the associated change, ensuring all related artifacts and specs are in a consistent, finalized state.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-profile-update'.

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, validate artifact and task completion status, assess delta spec synchronization, and move the finalized change to a timestamped archive location for a clean project history.

What is change management spec synchronization in OpenSpec?

Spec synchronization assesses delta specs against main specs during the archiving process, optionally syncing them to ensure all related artifacts and specifications remain in a consistent, finalized state.

Do I need the openspec CLI to archive a finalized change?

Yes, you need the openspec CLI installed to perform status checks and list available changes before moving completed artifacts and tasks to the timestamped archive directory.

How to validate completion status before archiving a change?

The archiving process validates completion status by verifying that all related artifacts and tasks are finalized, assessing delta spec synchronization before moving the change to the archive location.

What's the best way to organize completed change artifacts in project history?

Automated archiving organizes project history by moving completed changes to an archive directory with a timestamped name, ensuring all artifacts and specs are validated and finalized.