skills.rest
zhentingWu-wzt
zhentingWu-wztCOMMUNITY
Explore all skills by this author →
GitHub

comet-archive

Merge verified OpenSpec delta specifications into the main project documentation and archive them.

6|Updated May 25, 2026
Search Tags:#workflow#devops#archiving#lifecycle#openspec#comet
One-click install
npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-archive-zhentingwu-wzt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-archive
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/comet-archive
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-archive-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill manages the final stage of the Comet development lifecycle, ensuring that verified changes are safely merged into the main specification and properly archived to maintain project integrity.

Core Features & Use Cases

  • Automated Archiving: Moves completed changes to the archive directory while updating metadata.
  • Spec Synchronization: Merges delta specifications into the main project spec using OpenSpec semantics.
  • Lifecycle Enforcement: Ensures all verification steps are passed and provides a final safety gate before irreversible file operations.

Quick Start

Execute the comet-archive skill to finalize the current change and move it to the archive directory.

Frequently Asked Questions about comet-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed development changes and merge delta specifications?▼

You can archive completed development changes by merging delta specifications into main project documentation using OpenSpec semantics, then moving verified changes to the archive directory to maintain historical records.

What is the Comet workflow final phase for project lifecycle management?▼

The Comet workflow final phase finalizes verified development changes by applying automated archival, synchronizing main project specifications, and enforcing lifecycle state transitions to ensure project integrity.

Do I need to complete all verification steps before archiving changes in OpenSpec?▼

Yes, successful completion of all preceding verification stages is required before archiving changes, as lifecycle enforcement provides a final safety gate before irreversible file operations are executed.

How does spec synchronization work when finalizing development changes?▼

Spec synchronization works by merging delta specifications into the main project spec using OpenSpec semantics, ensuring consistent state transitions while updating metadata during the archival process.

Can I use automated archiving to maintain project integrity without manual file operations?▼

Yes, automated archiving moves completed changes to the archive directory while updating metadata, applying OpenSpec delta semantics to ensure consistent state transitions and historical record keeping without manual intervention.

Related Skills

Explore More Software Engineering Skills→
RyanCallahan312RyanCallahan312

openspec-sync-specs

Synchronize delta specs into main OpenSpec specifications with intelligent merging.

Community
Advanced
vobasevobase
59

status-machines

Validate status transitions against explicit maps and record audit entries.

Official
Intermediate
re-cinqre-cinq
20

opsx

Automates the OpenSpec change lifecycle from proposal to archival.

Official
Advanced
zhentingWu-wztzhentingWu-wzt
6

openspec-sync-specs

Merge delta specification changes into main project documentation.

Community
Advanced