spectra-archive

Archive completed experimental changes with delta specs and artifact provenance.

45|3|Updated Jan 20, 2026

Search Tags:#workflow #provenance #artifacts #archive #change-management #spectra #delta-specs

Ready to run

npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-archive-yudefine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spectra-archive
Source: https://github.com/YuDefine/nuxt-supabase-starter/tree/main/.claude/skills/spectra-archive
Command: npx skills add https://github.com/YuDefine/nuxt-supabase-starter --skill spectra-archive-yudefine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in experimental workflows by capturing artifacts, delta specs, and provenance into a centralized archive.

Core Features & Use Cases

End-to-end archiving of a labeled spectra change, including artifact status, delta spec assessment, and archival snapshot.
Guardrails ensure only complete changes are archived, with optional syncing and conflict handling.
Useful for teams needing reproducible change records, auditing, and closed-loop workflows.

Quick Start

Run spectra archive <change-name> to archive a completed change.

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 experimental workflow changes with delta specs and artifact provenance?▼

To archive completed changes, use a guided spectra workflow that captures artifacts, delta specs, and provenance into a centralized archive. It enforces change selection prompts, checks artifact status, and assesses delta-spec synchronization before performing the archival snapshot.

What is the best way to ensure only complete change artifacts are archived in experimental workflows?▼

The best way to archive complete change artifacts is using guardrails that enforce change selection prompts and check artifact status before archiving. This ensures only finished changes are captured, preventing incomplete experimental workflows from entering the archive.

Can I sync delta specs and handle conflicts during the spectra archive process?▼

Yes, you can optionally sync delta specs and handle conflicts during the spectra archive process. The workflow assesses delta-spec synchronization and performs the archive with optional flags to manage conflicts and ensure change records remain reproducible.

When do I need to archive change provenance for auditing in experimental workflows?▼

You need to archive change provenance for auditing when a change is finished and your team requires reproducible change records. Archiving captures artifact status, delta specs, and provenance, enabling closed-loop workflows and reliable auditing for experimental changes.

Does the spectra archive workflow work for teams needing repeatable archiving of experimental changes?▼

Yes, the spectra archive workflow is designed for teams managing experimental changes who need repeatable archiving. It provides end-to-end archiving of labeled changes, including artifact status checks, delta spec assessment, and an archival snapshot for closed-loop workflows.