skills.rest
Larusso
LarussoCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed experimental workflow changes after verifying artifact and task statuses.

42|10|Updated Mar 7, 2018
Search Tags:#workflow#task management#archive#change management#openspec#specification sync
One-click install
npx skills add https://github.com/Larusso/unity-version-manager --skill openspec-archive-change-larusso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Larusso/unity-version-manager/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/Larusso/unity-version-manager --skill openspec-archive-change-larusso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes within the experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to a designated archive location.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After implementing a new feature and testing it thoroughly, use this Skill to archive the associated change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Quick Start

Archive the change named 'user-authentication-module'.

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

To archive completed changes in an experimental workflow, you must verify artifact and task completion statuses, optionally sync delta specifications, and move the change to an archive directory using the openspec CLI.

What is delta specification sync and when do I need it?▼

Delta specification sync assesses and optionally merges delta specifications with main specifications. It is needed when archiving a change to ensure your project's main specifications remain up-to-date before the change is moved.

Do I need the openspec CLI to archive a change?▼

Yes, you need the openspec CLI installed. This dependency is required because the archiving process uses it to check artifact and task completion statuses and to perform potential specification synchronizations.

Can I archive a change if artifact or task completion is not verified?▼

No, archiving a change requires verifying artifact and task completion status first. The workflow prevents moving changes to the archive directory until all related artifacts and tasks are fully accounted for.

What is the best way to manage completed feature changes in OpenSpec?▼

The best way to manage completed feature changes in OpenSpec is to use an automated archiving workflow that verifies task completion, syncs delta specifications with main specifications, and moves the change to a designated archive directory.

Related Skills

Explore More Software Engineering Skills→
dorriodorrio

openspec-new-change

Create a new change directory and determine workflow schema in OpenSpec.

Community
Intermediate
Sharper-FlowSharper-Flow
4

adv-reflect

Analyze archived engineering change data to generate structured postmortem reports.

Official
Advanced
typemdtypemd
9

openspec-archive-change

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

Official
Advanced
chenwei791129chenwei791129
1

spectra-ingest

Updates Spectra change artifacts by ingesting external plan files or conversation context.

Community
Advanced