openspec-archive-change

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

Archive completed openspec workflow changes after validating artifacts and task status.

5|Updated Sep 17, 2022

Search Tags:#workflow #cli #archive #openspec #change-management #spec-sync

Ready to run

npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-archive-change-kevinxo328

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kevinxo328/mercari-scraper/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-archive-change-kevinxo328

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps finalize and archive completed changes in an experimental openspec workflow so teams can retire implemented changes cleanly and keep the workspace organized.

Core Features & Use Cases

Guided Selection: Prompts the user to select an active change when no name is provided, preventing accidental archival.
Completion Validation: Checks artifact completion via openspec status and inspects task lists for incomplete tasks, warning the user when issues exist.
Spec Sync Assessment: Compares delta specs to main specs and offers to sync changes before archiving, preserving spec integrity.
Use Case: When a feature branch's change is implemented and reviewed, run this Skill to confirm artifacts and tasks, optionally sync specs, and move the change into the archive with an auditable summary.

Quick Start

Use the openspec-archive-change skill to archive the completed change named my-change after confirming any warnings.

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 openspec changes safely, use a workflow that validates artifact completion via openspec status, checks for incomplete tasks, and optionally syncs delta specs to main specs before moving the change directory into an archive location.

What does openspec status check before archiving a change directory?▼

The openspec status command checks artifact completion within the change directory. The archival workflow inspects this status and reviews task lists to identify and warn about any incomplete tasks before proceeding.

How do I sync delta specs to main specs before archiving an openspec change?▼

Spec sync compares delta specs against main specs and offers to sync changes directly before archiving. This preserves spec integrity and ensures all modifications are properly captured in the main specification files.

Do I need the openspec CLI to archive experimental workflow changes?▼

Yes, archiving openspec changes requires access to the openspec CLI for running openspec list and openspec status commands. You also need a writable repository workspace to move the change directory into the archive location.

Can I archive an openspec change without specifying a change name?▼

Yes, the archival workflow provides guided selection and prompts you to select an active change when no name is provided. This prevents accidental archival of the wrong experimental workflow change directory.

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

When archiving an openspec change with incomplete tasks, the workflow inspects task lists and issues warnings about any unresolved issues. It confirms artifact completion and task status before moving the change into the archive.