openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

10|1|Updated Apr 10, 2019
One-click install
npx skills add https://github.com/GeTechG/LDYOM --skill openspec-archive-change-getechg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/GeTechG/LDYOM/tree/main/LDYOM2/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/GeTechG/LDYOM --skill openspec-archive-change-getechg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow by finalizing and moving them to archive, ensuring traceability and state preservation.

Core Features & Use Cases

  • Archive a finished OpenSpec change after implementation, preserving artifacts and delta specs for audit.
  • Validate artifact completion and task completion before archiving to prevent premature moves.
  • Sync delta specs with main specs when needed, with an optional confirmation flow.

Quick Start

Follow the prompts to select the change to archive and confirm archiving.

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 after implementation?

To archive an OpenSpec change, select the finished change and run validation checks on artifacts and tasks. The workflow assesses delta spec synchronization and prompts for confirmation before moving the change to the final archive.

When should I sync delta specs with main specs during change management?

You should sync delta specs with main specs during change management when the workflow detects pending delta updates before archiving. It assesses synchronization needs and offers an optional confirmation flow to finalize the merge.

Can I archive an OpenSpec change if artifacts or tasks are incomplete?

You cannot seamlessly archive an OpenSpec change with incomplete elements. The archiving process validates artifact and task completion first, actively prompting you to resolve any outstanding items before allowing the final move.

What is the best way to preserve traceability for archived workflow changes?

The best way to preserve traceability is archiving completed changes through the guided workflow. It finalizes the state, preserves associated artifacts and delta specs, and generates a summary for audit purposes.

Does the OpenSpec archiving workflow support custom change name selection?

Yes, the OpenSpec archiving workflow supports custom change name selection. It guides you through an optional naming step before proceeding to artifact completion checks and delta spec synchronization assessment.

Why does my OpenSpec archive process require a delta spec synchronization assessment?

The archive process requires a delta spec synchronization assessment to ensure main specs reflect implemented changes. This prevents state inconsistencies by deciding whether to sync deltas before finalizing the archive.