spectra-archive

Archive completed changes with the spectra CLI after validating artifacts and delta-spec synchronization.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-archive-bruno-yu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-archive
Source: https://github.com/Bruno-Yu/portfolio/tree/main/.cursor/skills/spectra-archive
Command: npx skills add https://github.com/Bruno-Yu/portfolio --skill spectra-archive-bruno-yu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes and preserve their provenance by coordinating artifact statuses, delta-spec synchronization, and openspec data during the archival process.

Core Features & Use Cases

  • Interactive selection of the target change when not explicitly provided
  • Artifact and task status checks to ensure completeness before archiving
  • Delta-spec synchronization assessment and optional syncing
  • Safe cleanup and preservation of openspec metadata during archive
  • Clear post-archive summary and archival path

Quick Start

Invoke the spectra archive workflow by providing or selecting a change name to begin the archival process.

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 while preserving openspec data safely?

Archiving changes safely involves validating artifact statuses, task completeness, and delta-spec synchronization via the spectra CLI before executing the archive command to preserve openspec metadata and provenance.

What is delta-spec synchronization and why is it needed before archiving?

Delta-spec synchronization ensures artifact changes are consistent before archiving by assessing delta specs to decide if syncing is required, preventing data loss during the openspec archive cleanup process.

How do I check artifact and task status before running spectra archive?

Run spectra status to check artifact and task completeness before archiving, ensuring all completed changes are validated and synchronized to avoid archiving incomplete or inconsistent openspec data.

Can I archive a change interactively if I don't provide a change name?

Yes, you can interactively select the target change when a change name is not explicitly provided, allowing the spectra CLI to prompt for selection before validating and archiving the completed openspec data.

What happens to openspec metadata after archiving completed changes?

After archiving, openspec metadata is safely preserved and a clear post-archive summary is provided, including the archival path, ensuring provenance is maintained during the cleanup of completed changes.

When should I not use the spectra archive workflow for change management?

Avoid archiving when artifact or task statuses are incomplete or when delta specs are out of sync, as the workflow requires validated, synchronized changes to safely preserve openspec data during the archival process.