openspec-archive-change

Archive completed openspec changes after validating artifacts and task status.

4|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/valuedriven/devai --skill openspec-archive-change-valuedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/valuedriven/devai/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/valuedriven/devai --skill openspec-archive-change-valuedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive closed changes in the experimental workflow, ensuring a clean, auditable history.

Core Features & Use Cases

  • Provides a guided, rule-based archive process for openspec changes.
  • Validates artifact and task completion, prompts for needed confirmations, and optionally syncs delta specs before archiving.
  • Maintains an organized archive directory with date-stamped filenames for easy retrieval.

Quick Start

Archive a completed change after verifying all artifacts and tasks are done and optionally sync delta specs if available.

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 while maintaining an audit trail?

You can archive completed openspec changes by verifying artifact completion and task status, optionally syncing delta specs, then executing the archive operation to generate a date-stamped file for a clean audit trail.

What happens if I try to archive an openspec change with missing prerequisites?

When archiving an openspec change with missing prerequisites, the process pauses and prompts you for required confirmations, verifying artifact completion and task status to prevent broken audit trails.

Can I sync delta specs automatically before archiving an openspec change?

Yes, you can optionally sync delta specs during the openspec change archiving process, which assesses synchronization status during its validation checks to ensure archived artifacts reflect the latest specifications.

How are archived openspec changes organized for easy retrieval?

Archived openspec changes are stored in a dedicated directory using date-stamped filenames, ensuring a clean, auditable history that supports easy retrieval and organized workflow management over time.

When do I need to use a rule-based archive process for spec changes?

You need a rule-based archive process for spec changes when operating within the openspec experimental workflow, enforcing artifact completion and task status validation to maintain a clean, auditable history of closed changes.