openspec-archive-change

Archive completed changes with date-stamped names after verifying artifact and task completion.

1|Updated May 26, 2025
One-click install
npx skills add https://github.com/StrayDragon/llman --skill openspec-archive-change-straydragon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/StrayDragon/llman/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/StrayDragon/llman --skill openspec-archive-change-straydragon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Automated Archiving: Finalizes and moves completed changes to an archive directory.
  • Status Verification: Checks artifact and task completion before archiving.
  • Delta Spec Sync: Evaluates and prompts for synchronization of delta specifications with main specifications.
  • Use Case: After successfully implementing a new feature and testing all associated artifacts and tasks, use this Skill to formally archive the change, making it a part of the project's historical record.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-auth'.

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, this skill verifies artifact and task completion, evaluates delta specification synchronization, and moves the change to an archive directory with a date-stamped name. You can select the target change and confirm incomplete items interactively.

What happens if artifact or task completion is not verified before archiving a change?

If artifact or task completion is not verified, the skill prompts you for confirmation on incomplete items before proceeding. This ensures you do not accidentally archive an unfinished change without explicitly acknowledging missing artifacts or pending tasks.

How does delta specification synchronization work when archiving a change?

Delta specification synchronization evaluates whether the change's delta specs need to be merged with main specifications. The skill evaluates this status during archiving and prompts you to handle the synchronization to maintain a clean and organized project history.

What is the best way to manage change history and keep completed tasks organized?

To manage change history and keep tasks organized, use this skill to finalize completed changes. It moves verified changes into an archive directory using a date-stamped naming convention, making them a formal part of the project's historical record.

Do I need any specific version control tools to use this change management skill?

No specific version control tools are required as dependencies. The skill independently handles archiving completed changes by verifying artifacts, evaluating delta specs, and organizing the project history into a date-stamped archive directory.