openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: hadenlabs

Archive completed OpenSpec changes with artifact checks and delta spec synchronization.

1|Updated Dec 9, 2024

Search Tags:#workflow #archive #openspec #artifact #change-management #delta-spec #archive-management

Ready to run

npx skills add https://github.com/hadenlabs/tasks --skill openspec-archive-change-hadenlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hadenlabs/tasks/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/hadenlabs/tasks --skill openspec-archive-change-hadenlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow to keep histories clean, auditable, and easy to reference.

Core Features & Use Cases

Guided archival workflow: prompts for change selection, checks artifact and task completion, and handles delta spec synchronization when present.
Safe archiving: preserves metadata and moves changes to an archive folder with date-stamped naming.
Use Case: When a change is implemented and validated, archive it to signal completion and preserve a reference for future audits.

Quick Start

Select the change to archive if not provided, then follow the steps to verify artifacts, assess delta specs, optionally sync, and move the change into the archive.

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 to maintain project hygiene?▼

To archive completed OpenSpec changes, select the change, verify artifact and task completion, assess optional delta specs, and move the change into an archive folder with date-stamped naming for a verifiable history.

When should I archive a change in the OpenSpec workflow?▼

You should archive a change in the OpenSpec workflow when the change is fully implemented and validated, ensuring artifact checks and delta spec synchronization are complete to signal finalization and preserve an audit reference.

Does archiving OpenSpec changes require the openspec CLI?▼

Yes, archiving OpenSpec changes requires using the openspec CLI to handle artifact checks, optional delta spec synchronization, and the final movement of changes into the archive directory.

What happens to delta specs when archiving an OpenSpec change?▼

When archiving an OpenSpec change, the workflow checks for optional delta specs and synchronizes them when present, ensuring metadata is preserved before moving the change to the archive folder.

Can I safely archive an OpenSpec change before task completion?▼

No, safe archiving requires checking artifact and task completion first. The guided workflow prompts for confirmation to ensure changes are fully implemented and validated before moving them to the archive.

What is the best way to preserve a verifiable history of completed OpenSpec changes?▼

The best way to preserve a verifiable history is using a guided archival workflow that moves completed changes to an archive folder with date-stamped naming, keeping histories clean, auditable, and easy to reference.