openspec-archive-change

Archive completed OpenSpec changes with verified artifacts and delta specs.

30|4|Updated Aug 2, 2024
One-click install
npx skills add https://github.com/belingud/gptcomet --skill openspec-archive-change-belingud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/belingud/gptcomet/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/belingud/gptcomet --skill openspec-archive-change-belingud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow to preserve state after implementation, ensuring changes are moved to a structured archive with artifacts and delta specs validated.

Core Features & Use Cases

  • Prompted selection of a change when not provided
  • Artifact and task status checks via OpenSpec CLI and related files
  • Delta spec assessment against main specs with optional sync
  • Safe archival into openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration
  • Summary reporting including archive location and status

Quick Start

Run the OpenSpec archive workflow to select a change, verify artifacts and tasks, assess delta specs, and move the change to openspec/changes/archive/YYYY-MM-DD-<name>.

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 after implementation?

To archive completed OpenSpec changes, you run the archive workflow which verifies artifact and task statuses, assesses delta specs, and moves the change to a date-stamped directory. It ensures safe archival into openspec/changes/archive/YYYY-MM-DD-<name>.

What does the OpenSpec archival process check before moving a change?

The OpenSpec archival process checks artifact and task statuses via the CLI, validates task completion, and compares delta specs against main specs. It optionally syncs delta specs before moving the change to the structured archive.

Do I need the OpenSpec CLI to archive delta specs and changes?

Yes, the OpenSpec CLI is required to archive changes. The workflow relies on the CLI to check status, validate tasks, compare specs, and move the change to the archive directory.

Can I synchronize delta specs with main specs during OpenSpec archival?

Yes, you can synchronize delta specs during OpenSpec archival. The workflow assesses delta specs against main specs and optionally syncs them before moving the change to the archive directory.

How are configuration files preserved when archiving OpenSpec changes?

Configuration files are preserved during OpenSpec archival by keeping the .openspec.yaml file intact. The workflow moves the change to openspec/changes/archive/YYYY-MM-DD-<name> while ensuring this configuration is safely maintained.

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

Archiving an OpenSpec change with incomplete tasks triggers validation checks via the CLI. The workflow verifies task completion and artifact statuses, ensuring changes are only archived after successful validation.