openspec-archive-change

Archive completed changes after verifying artifact and task completion status.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/nuitsjp/teams-board --skill openspec-archive-change-nuitsjp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/nuitsjp/teams-board/tree/main/.rulesync/skills/openspec-archive-change
Command: npx skills add https://github.com/nuitsjp/teams-board --skill openspec-archive-change-nuitsjp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows users to archive completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Workflow Archiving: Finalizes and moves completed changes to an archive directory.
  • Status Checks: Verifies artifact and task completion before archiving.
  • Spec Syncing: Optionally syncs delta specifications with main specifications.
  • Use Case: After successfully implementing a new feature and testing it thoroughly, you can use this Skill to archive the associated change, marking it as complete and organized.

Quick Start

Use the openspec archive change skill to archive the change named 'feature-x'.

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 change in an experimental workflow?

Archiving a completed change involves verifying artifact and task completion status, optionally synchronizing delta specifications with main specifications, and moving the change directory to an archive location.

What happens to delta specifications when archiving completed changes?

When archiving completed changes, the process facilitates optional synchronization of delta specifications with main specifications to ensure your project history remains clean and aligned before finalizing the archive.

Can I archive an experimental workflow change if tasks are not fully completed?

No, archiving requires successful status checks. The process verifies artifact and task completion before moving the change directory, ensuring only fully implemented and tested changes are archived.

How do I move a completed feature directory to an archive location?

You can move a completed feature directory by running the archive change process, which prompts you for confirmation and selection of changes before relocating the directory to your archive location.

Does the change management archiving process require user confirmation?

Yes, the change management archiving process handles user prompts for confirmation and selection of changes, ensuring you maintain manual control over which completed changes are finalized and moved.