spectra-archive

Archive completed Spectrum changes to date-stamped openspec/changes/archive paths.

33|8|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-archive-psychquant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-archive
Source: https://github.com/PsychQuant/che-ical-mcp/tree/main/.agents/skills/spectra-archive
Command: npx skills add https://github.com/PsychQuant/che-ical-mcp --skill spectra-archive-psychquant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change to the Spectrum archive store to preserve provenance and enable audits.

Core Features & Use Cases

  • Automates the archival workflow for completed changes, including artifact checks, delta-spec validation, and archive path management.
  • Prompts for change selection when ambiguous and presents a clear summary of the archive outcome for governance and auditing.
  • Maintains an auditable archive structure under openspec/changes/archive with a date-based directory.

Quick Start

Archive a change named "example-change" using the spectra-archive workflow.

Frequently Asked Questions about spectra-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed changes to preserve provenance and enable auditing?

Archiving completed changes preserves provenance and enables auditing by moving finalized artifacts to openspec/changes/archive with date-stamped paths. This workflow handles change selection, artifact completion checks, and delta-spec synchronization assessment to maintain a verifiable audit trail.

What's the best way to manage change archival workflows with delta-spec synchronization checks?

Managing change archival workflows requires validating delta-spec synchronization before finalizing the archive. This process checks artifact completion, assesses delta-spec alignment, and executes archiving to ensure completed changes meet governance and auditing requirements.

Do I need the spectra CLI to archive changes to the openspec directory?

You need the spectra CLI to archive changes to the openspec directory. The archival workflow requires this CLI to validate prerequisites, prompt for user input when change selection is ambiguous, and execute the final archiving process.

How does artifact completion validation work before archiving a change?

Artifact completion validation checks whether all required artifacts are finalized before archiving a change. This ensures only fully completed changes are moved to the archive store, preventing incomplete workflows from compromising provenance and audit integrity.

Can I select a specific completed change to archive when multiple changes exist?

You can select a specific completed change to archive when multiple changes exist. The workflow prompts for change selection when the target is ambiguous, ensuring the correct change is archived with its delta-specs and artifacts.

Why does my change archival process require date-stamped directory paths?

Change archival requires date-stamped directory paths to maintain an auditable archive structure under openspec/changes/archive. This structure preserves provenance by chronologically organizing completed changes for governance and auditing purposes.