skills.rest
nfe
nfeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archives a completed OpenSpec experimental workflow change after validating tasks and artifacts.

139|27|Updated Nov 9, 2014
Search Tags:#workflow#archive#openspec#spec sync#delta specs#artifact status#ops tooling
One-click install
npx skills add https://github.com/nfe/client-nodejs --skill openspec-archive-change-nfe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/nfe/client-nodejs/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/nfe/client-nodejs --skill openspec-archive-change-nfe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize an experimental workflow change by archiving it only after checking artifact and task completion, with an optional (recommended) spec delta sync.

Core Features & Use Cases

  • Select the correct change: If a change name is not provided, it prompts you to choose from active changes.
  • Verify completion readiness: Checks artifact status via the OpenSpec CLI and warns about incomplete artifacts or tasks.
  • Optional delta-spec synchronization: Detects delta specs, summarizes required sync actions, and lets you decide whether to sync before archiving.
  • Archive safely with date-stamped naming: Moves the change directory into an archive location using a YYYY-MM-DD-<change-name> target and fails if that target already exists.

Quick Start

Ask the assistant to archive the completed OpenSpec experimental change named "Add OAuth support" in the current workflow.

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 workflow changes safely?▼

To archive completed OpenSpec workflow changes safely, the system validates artifact and task completion via CLI status checks, optionally syncs delta specs, then moves the directory into an archive with date-stamped naming.

What happens if I try to archive an OpenSpec change with incomplete artifacts?▼

Archiving incomplete artifacts triggers a warning. The system checks artifact and task status via OpenSpec CLI commands before proceeding, ensuring changes are not prematurely retired without completion verification.

Do I need to run openspec-sync-specs before archiving a delta spec?▼

Running openspec-sync-specs before archiving is optional but recommended. The system detects delta specs, summarizes required sync actions, and lets you decide whether to synchronize before moving the change directory.

Can I archive an OpenSpec change without specifying the change name?▼

Yes, you can archive without specifying a name. If a change name is not provided, the system prompts you to select from a list of active experimental workflow changes before proceeding with the archiving process.

Why does archiving an OpenSpec change fail when the target directory already exists?▼

Archiving fails if the target directory already exists to prevent overwriting. The system uses a YYYY-MM-DD-<change-name> naming convention for the archive target, ensuring unique date-stamped retirement paths.

Related Skills

Explore More Software Engineering Skills→
formioformio
6

openspec-archive-change

Archive completed changes in an openspec experimental workflow.

Official
Intermediate
johnqxujohnqxu

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and delta specs.

Community
Advanced
factorial-iofactorial-io
14

openspec-archive-change

Finalize and archive completed changes by verifying artifacts and tasks.

Official
Intermediate
typemdtypemd
9

openspec-archive-change

Archive completed experimental workflow changes with validation and date-stamped directories.

Official
Advanced