skills.rest
sitdownkevin
sitdownkevinCOMMUNITY
Explore all skills by this author →
Website𝕏@sitdownkevinGitHub

openspec-archive-change

Archive completed OpenSpec changes into dated directories with status verification.

1|Updated May 7, 2024
Search Tags:#workflow#archive#openspec#prompting#change-management#delta-spec#status-check
One-click install
npx skills add https://github.com/sitdownkevin/blog-next --skill openspec-archive-change-sitdownkevin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/sitdownkevin/blog-next/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/sitdownkevin/blog-next --skill openspec-archive-change-sitdownkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes by orchestrating status checks, task validation, optional delta-spec sync, and safe archiving to a dated archive directory, maintaining a clear history.

Core Features & Use Cases

  • Guides the user through selecting an active change to archive.
  • Verifies artifact completion and task completion, prompting for confirmation on any incomplete items.
  • Checks for delta specs and, when present, assesses sync needs against main specs, offering an explicit merge/sync path.
  • Performs the archive operation into openspec/changes/archive/YYYY-MM-DD-<name>, preserving metadata and optional delta-sync status.
  • Presents a concise summary of actions taken and the archive location for auditability.

Quick Start

Archive the current change after implementation by moving its folder to the archive location with a dated 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 completed OpenSpec changes safely?▼

To archive completed OpenSpec changes safely, the workflow verifies artifact and task completion, checks delta-spec synchronization, and moves the change into a dated archive directory using the openspec CLI with user confirmation prompts.

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

When archiving an OpenSpec change with incomplete tasks, the process identifies incomplete artifacts or tasks and prompts the user for explicit confirmation before proceeding with the archive operation to prevent data loss.

How does delta-spec synchronization work during change archiving?▼

Delta-spec synchronization during change archiving assesses sync needs against main specs when delta specs are present, offering an explicit merge path before moving the change folder to the dated archive directory.

Do I need the openspec CLI to archive change management workflows?▼

Yes, the openspec CLI is required to perform status verification and delta-spec syncing operations when archiving a completed change management workflow into the dated archive directory.

Where are archived OpenSpec changes stored?▼

Archived OpenSpec changes are stored in the openspec/changes/archive/YYYY-MM-DD-<name> directory, preserving metadata, delta-sync status, and providing a concise summary of actions taken for auditability.

Related Skills

Explore More Software Engineering Skills→
hossam7amdyhossam7amdy

openspec-archive-change

Archive completed openspec changes into date-stamped folders after validating artifacts and tasks.

Community
Advanced
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

Official
Advanced
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
KisthannyKisthanny
1

openspec-archive-change

Archive completed OpenSpec change directories after validating readiness and preserving workflow context.

Community
Advanced