openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and task completion.

10|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-archive-change-joannanowakowska
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/joannanowakowska/plannning-poker-app/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-archive-change-joannanowakowska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize a completed OpenSpec change by checking readiness, confirming any missing artifacts or tasks, and moving the change into the archive in a controlled way.

Core Features & Use Cases

  • Change selection: Prompts the user to choose the exact active change when one is not already specified.
  • Completion checks: Verifies artifact status and task completion before archiving, and warns when work is still incomplete.
  • Delta spec handling: Assesses whether delta specs need syncing before archive and guides the user through the decision.
  • Archive execution: Moves the change directory into a dated archive location while preserving the workflow context.
  • Use Case: A team finishes implementing a feature and wants to safely archive the related OpenSpec change without losing the associated metadata or skipping validation.

Quick Start

Ask the openspec archive-change skill to archive the completed change named authentication-flow.

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 safely?

To archive an OpenSpec change safely, the workflow validates artifact status and task completion, prompts for delta spec sync, and relocates the change root into a dated archive path using the openspec CLI.

What happens to incomplete tasks when archiving an OpenSpec change?

When archiving an OpenSpec change with incomplete tasks, the workflow performs completion checks and issues warnings about missing artifacts or unfinished work before proceeding with the archive relocation.

Does archiving an OpenSpec change require syncing delta specs first?

Archiving an OpenSpec change assesses whether delta specs need syncing before archive and guides the user through the decision, ensuring spec synchronization is handled before the change directory is moved.

Can I select a specific active change to archive if multiple exist?

Yes, the OpenSpec archive workflow prompts the user to choose the exact active change to archive when a specific change name is not already specified in the command input.

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

Yes, the openspec CLI is required to archive workflow changes, as it handles the selection, validation warnings, and relocation of the change root into the experimental workflow repository's dated archive directory.