openspec-archive-change

Archive completed openspec changes after verifying artifacts and tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage the experimental workflow by archiving completed changes, ensuring a clean and organized project history.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to an archive directory, preventing clutter.
  • Status Checks: Verifies artifact and task completion before archiving, providing warnings for incomplete items.
  • Spec Syncing: Assesses and optionally syncs delta specs with main specs before archiving.
  • Use Case: After implementing a new feature and testing it, use this Skill to formally archive the development change, ensuring all related artifacts and tasks are accounted for.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-profile-update'.

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?

To archive completed changes in an OpenSpec workflow, the Skill moves verified changes to an archive directory. It assesses delta spec synchronization and prompts for user confirmation before completing the archival process.

What happens to incomplete tasks when archiving a change?

When archiving a change, the Skill performs status checks and provides warnings for incomplete tasks or artifacts. It verifies completion before moving the change to the archive directory.

Does archiving a change sync delta specs with main specs automatically?

Archiving a change assesses delta spec synchronization and optionally syncs delta specs with main specs. It prompts for user confirmation before moving the change to the archive directory.

Do I need the openspec CLI to archive completed changes?

Yes, you need the openspec CLI installed to archive completed changes. The Skill requires the CLI for performing status checks and listing available changes before archiving.

Can I prevent project clutter by archiving old workflow changes?

You can prevent project clutter by archiving old workflow changes using this Skill. It moves completed changes to an archive directory, ensuring a clean and organized project history.

Why does the change archiving process prompt for user confirmation?

The change archiving process prompts for user confirmation to ensure all artifacts and tasks are verified and delta specs are synced. This prevents accidental archival of incomplete or unsynchronized changes.