openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/MiDouTech/myTapd --skill openspec-archive-change-midoutech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/MiDouTech/myTapd/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/MiDouTech/myTapd --skill openspec-archive-change-midoutech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finalizes and archives a completed change in an openspec experimental workflow by verifying artifacts and tasks, optionally assessing and syncing delta specs, and safely moving the change directory to a date-prefixed archive location.

Core Features & Use Cases

  • Interactive selection: Prompt the user to choose an active change when no name is provided, never auto-selecting.
  • Artifact and task validation: Run openspec status to check artifact completion and inspect tasks files for incomplete items, requiring confirmation if warnings exist.
  • Delta spec analysis and sync options: Detect delta specs, compare them to main specs, summarize adds/modifications/removals, and offer sync or skip choices; can invoke a sync task if requested.
  • Safe archival operation: Create archive directories, detect name collisions, move the change directory while preserving metadata, and display a clear summary of actions and warnings.

Quick Start

Archive the change named my-change, verifying artifacts and tasks and syncing delta specs if needed before moving it to openspec/changes/archive with a date-prefixed 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 a completed openspec change and move its directory?

To archive a completed openspec change, this skill verifies artifacts and tasks, optionally syncs delta specs, and safely moves the change directory to a date-prefixed archive location under openspec/changes/archive.

What happens to delta specs when finalizing an openspec workflow change?

When finalizing an openspec workflow change, delta specs are detected and compared against main specs in openspec/specs. The skill summarizes additions, modifications, and removals, offering a choice to sync or skip.

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

Yes, the openspec CLI is required to archive experimental workflow changes. The skill uses CLI listing and status commands to check artifact completion and inspect task files before moving directories.

Can I automatically select an active change to archive without providing a name?

No, active changes are never auto-selected. When no change name is provided, the skill prompts you with an interactive selection to choose which specific change to archive.

What if my openspec change has incomplete tasks or artifact warnings?

If artifact validation or task inspections reveal incomplete items or warnings, the skill requires your explicit confirmation before proceeding with the archival operation to ensure safe finalization.

How does openspec archival handle directory name collisions?

During the archival operation, the skill detects name collisions in the archive directory. It safely moves your change directory while preserving metadata and displays a clear summary of actions and warnings.