openspec-archive-change

Archive completed changes with artifact checks and delta-spec synchronization.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/raiden076/Prism --skill openspec-archive-change-raiden076
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/raiden076/Prism/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/raiden076/Prism --skill openspec-archive-change-raiden076

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow, ensuring a clear, auditable handoff from implementation to archival storage.

Core Features & Use Cases

  • End-to-end archiving: Move finished changes into a structured archive directory with date-stamped naming while preserving metadata and .openspec.yaml.
  • Artifact and task validation: Checks artifacts and tasks completion before archiving, with optional user confirmation for edge cases.
  • Delta-spec alignment: Assesses delta specs against main specs and harmonizes changes when requested, ensuring synchronization history is maintained.

Quick Start

Run the archive workflow to move the completed change into the archive after confirming all artifacts and tasks are finished.

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 workflow changes with guardrails?

Archiving completed changes requires validating artifacts and tasks first. The workflow moves finished changes into a structured archive directory with date-stamped naming, preserving metadata and .openspec.yaml for an auditable handoff.

When do I need to archive delta specs in change management?

You need to archive delta specs when handing off from implementation to archival storage. The skill assesses delta specs against main specs and harmonizes changes to maintain synchronization history before final archival.

How do I validate artifacts and tasks before archiving changes?

Artifact validation before archiving involves automated checks for task completion. The workflow enforces guardrails by verifying all artifacts are finished, with optional user confirmation prompts for handling edge cases.

Can I synchronize delta specs against main specs during archival?

Yes, delta-spec synchronization is supported during archival. The workflow assesses delta specs against main specs and harmonizes changes when requested, ensuring synchronization history is maintained throughout the process.

What happens if artifact checks fail during change archival?

If artifact checks fail, the archiving process halts to enforce guardrails. The workflow prevents incomplete changes from moving to archival storage, requesting user confirmation only for approved edge cases before proceeding.