openspec-archive-change

Archive completed OpenSpec changes with date-stamped folders via the OpenSpec CLI.

221|96|Updated May 18, 2022
One-click install
npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-archive-change-sap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/SAP/e-mobility-charging-stations-simulator/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/SAP/e-mobility-charging-stations-simulator --skill openspec-archive-change-sap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a safe, automated way to archive finished OpenSpec changes, ensuring traceability and clean project history.

Core Features & Use Cases

  • Archive completed change directories under openspec/changes/archive with a date-stamped folder.
  • Validate artifacts and tasks status via openspec status to inform users before archiving.
  • Preserve the original OpenSpec metadata when moving to the archive, and optionally sync delta specs if applicable.

Quick Start

Use the openspec-archive-change skill to archive a completed OpenSpec change. If you don't provide a change name, the tool will prompt you to select one from active changes and will guide you through artifact and task checks before archiving.

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 to preserve project history?

Archive OpenSpec changes by moving completed change directories under openspec/changes/archive with a date-stamped folder, preserving the original .openspec.yaml metadata to prevent rework and maintain traceability.

What happens to the .openspec.yaml file when I archive a change?

When archiving an OpenSpec change, the original .openspec.yaml metadata is preserved during the move to the archive directory, ensuring the change history and configuration remain intact for future reference.

How do I check artifact and task status before archiving an OpenSpec change?

Validate artifacts and task status before archiving by running the openspec status command, which checks completion states and informs you of any pending items that need resolution prior to archiving.

Can I archive an OpenSpec change without specifying the change name?

Yes, if no change name is provided, the archiving tool prompts you to select one from the list of active OpenSpec changes, then guides you through artifact and task checks before completing the archive process.

Does the OpenSpec archive process support delta spec synchronization?

Yes, the OpenSpec archive process optionally syncs delta specs during archiving, ensuring any incremental specification updates are synchronized before the completed change is moved to the archive directory.

When should I avoid archiving changes in the OpenSpec workflow?

Avoid archiving OpenSpec changes when artifact or task checks via openspec status indicate incomplete items, as archiving unfinished changes can lead to lost work and break the traceability of your project history.