openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: Atman

Archive completed OpenSpec changes to date-stamped paths while preserving metadata.

Updated Aug 27, 2026

Search Tags:#workflow #CLI #archive #openspec #change-management #artifact-status #delta-specs

Ready to run

npx skills add https://github.com/atman-33/skills --skill openspec-archive-change-atman-33

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/atman-33/skills/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/atman-33/skills --skill openspec-archive-change-atman-33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the archiving of completed OpenSpec changes in the experimental workflow, ensuring changes are finalized and preserved for reference.

Core Features & Use Cases

Change selection and archiving: Guides users through selecting a change and moving it to an archive with a date-stamped path.
Status checks: Validates artifact completion via openspec status, checks for remaining tasks, and reports any warnings without blocking the archive.
Delta spec sync assessment: Analyzes delta specs against main specs to determine if synchronization is needed, and can trigger sync if requested.
Audit-ready archive: Preserves important metadata (including .openspec.yaml) and returns a clear summary of the operation.

Quick Start

Use the openspec-archive-change skill to archive a completed change after implementation.

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 safely?▼

To archive completed OpenSpec changes, the Skill moves the finalized change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving the .openspec.yaml metadata and generating a clear operation summary.

What checks are needed before archiving an OpenSpec change?▼

Before archiving an OpenSpec change, the Skill runs openspec status to validate artifact completion, checks for remaining tasks, and reports any warnings without blocking the final archiving process.

How does delta spec synchronization work during OpenSpec change archiving?▼

Delta spec synchronization during archiving analyzes delta specs against main specs to determine if synchronization is needed, and can trigger the sync process automatically if requested by the user.

When do I need to archive a change in the OpenSpec workflow?▼

You need to archive a change in the OpenSpec workflow after implementation is fully complete, ensuring all artifacts are finalized, tasks are checked, and the change is ready for audit-ready preservation.

Does archiving an OpenSpec change preserve the .openspec.yaml metadata?▼

Yes, archiving an OpenSpec change preserves the .openspec.yaml file along with all important metadata, moving everything to a date-stamped archive path for future reference and audit readiness.

Can I archive an OpenSpec change if there are remaining task warnings?▼

Yes, you can archive an OpenSpec change with remaining warnings because the Skill reports any status warnings without blocking the archive, ensuring changes can be finalized even with non-critical issues.