openspec-archive-change

Archive completed OpenSpec changes into date-stamped directories with status validation.

Updated Mar 26, 2024
One-click install
npx skills add https://github.com/SHUSHU010829/shushu.tw --skill openspec-archive-change-shushu010829
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/SHUSHU010829/shushu.tw/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/SHUSHU010829/shushu.tw --skill openspec-archive-change-shushu010829

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow to keep a clean, auditable history and prevent rework.

Core Features & Use Cases

  • Archive a finished change to openspec/changes/archive with a date-stamped directory
  • Validate artifact and task completion before archiving
  • Optionally sync delta specs with main specs prior to archive

Quick Start

Archive a completed OpenSpec change after verifying artifacts are complete, optionally syncing delta specs, and moving the change to the 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 OpenSpec changes with a date-stamped directory?

To archive OpenSpec changes, provide the change name and the tool moves it to openspec/changes/archive/YYYY-MM-DD-<name>. It validates artifact and task completion before finalizing the archive and preserving .openspec.yaml.

What happens if artifacts or tasks are incomplete when archiving an OpenSpec change?

When artifacts or tasks are incomplete during OpenSpec archiving, the workflow checks status with openspec status and prompts for action. This prevents archiving unfinished changes and ensures an auditable record of fully implemented tasks.

Can I sync delta specs with main specs before moving a change to the archive?

Yes, you can optionally sync delta specs with main specs prior to archiving an OpenSpec change. This syncing happens before the change is finalized and moved to the archive directory to preserve spec consistency.

Why does archiving completed changes prevent rework in OpenSpec workflows?

Archiving completed OpenSpec changes prevents rework by finalizing implementations into an auditable history. It validates artifact completion and moves finished tasks to a dedicated archive, keeping the active workspace clean and preventing accidental duplicate effort.

Do I need to verify artifact status before archiving an OpenSpec change?

Yes, you need to verify artifact and task status before archiving an OpenSpec change. The workflow runs openspec status and will prompt you for action if artifacts are incomplete, ensuring only fully implemented changes are archived.

OpenSpec archive not working when tasks are incomplete, what are the limitations?

The OpenSpec archive workflow requires all artifacts and tasks to be complete before moving the change directory. If tasks are incomplete, it prompts for action instead of archiving, preventing unfinished changes from entering the auditable archive.