openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated Feb 6, 2024
One-click install
npx skills add https://github.com/081595/mynode --skill openspec-archive-change-081595
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/081595/mynode/tree/main/myproject/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/081595/mynode --skill openspec-archive-change-081595

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams finalize and archive an OpenSpec experimental change once implementation is complete, reducing manual checks and ensuring a consistent archive process.

Core Features & Use Cases

  • Guided Selection: Prompts the user to select an active change when the name is not provided to avoid accidental archiving.
  • Completion Validation: Uses openspec status to verify artifact completion and scans tasks for incomplete items, prompting the user on warnings.
  • Delta Spec Assessment & Sync: Compares change delta specs to main specs, summarizes differences, offers an optional sync, and then moves the change to a dated archive location.
  • Use Case: When a developer finishes a feature branch represented as an OpenSpec change, use this Skill to validate, optionally sync any spec deltas, and move the change to openspec/changes/archive with preserved configuration.

Quick Start

Use the openspec-archive-change skill to select a completed change, review warnings about artifacts or tasks, optionally sync delta specs, and archive the change to openspec/changes/archive.

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 OpenSpec workflow?

You can finalize a change by using the openspec CLI to validate artifacts and task completion, optionally sync delta specs, and move the change directory to openspec/changes/archive with preserved configuration.

What happens to incomplete tasks when I try to finalize an OpenSpec change?

When finalizing an OpenSpec change, the skill scans for incomplete tasks and prompts the user with warnings, requiring interactive confirmation before proceeding to archive the change.

Does the OpenSpec archive process sync delta specs to main specs automatically?

The archive process does not sync delta specs automatically; it compares change delta specs to main specs, summarizes differences, and offers an optional sync before moving the change to the archive directory.

Do I need the openspec CLI installed to archive experimental changes?

Yes, the openspec CLI is required to list and inspect changes in JSON format, validate artifact completion status, and finalize the change to the archive directory.

Can I archive a specific OpenSpec change without selecting from a list?

You can archive a specific change directly by providing its name, but if the name is omitted, the skill prompts you with guided interactive selection to prevent accidental archiving.