openspec-archive-change

Archive completed openspec changes after validating artifacts and tasks.

4|3|Updated Jan 16, 2023
One-click install
npx skills add https://github.com/sgiath/secp256k1 --skill openspec-archive-change-sgiath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/sgiath/secp256k1/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/sgiath/secp256k1 --skill openspec-archive-change-sgiath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed openspec changes to a persistent archive after ensuring all artifacts and tasks are finished, and delta specs are synchronized when applicable.

Core Features & Use Cases

  • Artifact status checks via openspec status to ensure all artifacts are done before archiving.
  • Task completion verification through tasks.md, warning on incomplete tasks with guardrails for proceeding.
  • Delta-spec assessment and optional synchronization using openspec-sync-specs when delta specs exist.
  • Archive creation with a timestamped directory under openspec/changes/archive and safe handling of existing targets.
  • Summary reporting that documents change name, schema, archive location, and whether specs were synced.

Quick Start

Archive a completed change by running the archive workflow to move the change directory into the archive after confirming all artifacts and tasks are complete.

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 openspec changes safely?

To archive completed openspec changes safely, the workflow validates artifact and task completion, checks delta specs, and moves the change directory into a timestamped archive folder under openspec/changes/archive.

What happens if I try to archive an openspec change with incomplete tasks?

When archiving an openspec change with incomplete tasks, the workflow verifies task completion through tasks.md and issues warnings, providing guardrails to help you decide whether to proceed with archiving.

Do I need to synchronize delta specs before archiving an openspec change?

You do not need to manually synchronize delta specs before archiving. The workflow performs a delta-spec assessment and offers optional synchronization using openspec-sync-specs when delta specs are detected.

How are archived openspec changes named and organized?

Archived openspec changes are organized into a timestamped directory created under openspec/changes/archive, applying date-based naming conventions with safe handling for any existing target directories to prevent conflicts.

Can I check artifact status before running the openspec archive workflow?

You can check artifact status before archiving by running openspec status. The archive workflow itself performs these artifact checks to ensure all items are done before moving the change to the persistent archive.

What summary is provided after archiving an openspec change?

After archiving an openspec change, the workflow provides a summary reporting the change name, schema, archive location, and whether specs were synced during the process.