spectra-archive

Archive completed repository changes with validated specs, artifacts, and metadata.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-archive-ycs77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-archive
Source: https://github.com/ycs77/gh-aw-todo-app/tree/main/.claude/skills/spectra-archive
Command: npx skills add https://github.com/ycs77/gh-aw-todo-app --skill spectra-archive-ycs77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reproducible, guarded workflow to archive completed repository changes so that specs, artifacts, tasks, and metadata are captured and moved to an archival location without accidental data loss or unsynced spec changes.

Core Features & Use Cases

  • Guided change selection: Prompts the user to choose an active change when none is provided and prevents accidental auto-selection.
  • Pre-archive validations: Checks artifact completion via spectra status, inspects task lists for incomplete items, and analyzes delta specs versus main specs to summarize required sync actions.
  • Flexible archive execution: Runs the spectra archive command with options to skip spec application, mark tasks complete, or bypass validation, and reports clear success, warning, or error summaries.
  • Use Case: When finalizing a feature change, validate artifacts and tasks, optionally sync delta specs to main specs, and create a dated archive directory preserving openspec metadata.

Quick Start

Archive a completed change by running the skill with a change name, for example: /spectra-archive add-auth.

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 change specs and artifacts in a repository workflow?

The workflow archives completed change specs by validating artifacts via status JSON outputs, inspecting task lists, and executing the archive command to move metadata safely, preventing data loss.

What happens to unsynced delta specs when I archive a change?

Unsynced delta specs are analyzed before archiving to summarize required sync actions. The workflow optionally invokes spec syncing to apply delta specs to main specs before running the final archive process.

Do I need the spectra CLI installed to archive repository changes?

Yes, archiving repository changes requires the spectra CLI available in PATH to parse list and status JSON outputs and invoke the archive and sync commands.

Can I skip validation and force archive a change with incomplete tasks?

Yes, you can bypass validation to force archive a change. The archive execution supports options to skip spec application, mark tasks complete, or bypass validation checks, though it reports warnings for incomplete items.

How does the guided change selection prevent accidental archiving?

Guided change selection prompts you to choose an active change when none is provided and prevents accidental auto-selection. This ensures you explicitly confirm the target change before any archival action runs.

What is the best way to verify artifact completion before archiving specs?

The best way to verify artifact completion is checking spectra status JSON outputs. The workflow inspects task lists for incomplete items and analyzes delta specs against main specs to summarize required sync actions before archiving.