comet-archive

Merge delta specs into main specs and archive completed changes using OpenSpec semantics.

2.7k|259|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-archive
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-archive
Command: npx skills add https://github.com/rpamis/comet --skill comet-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed delta changes by moving delta specs into main specs and finalizing OpenSpec merges, ensuring a clean historical record and guardrails against reusing archived work.

Core Features & Use Cases

  • Finalizes archival of a completed delta change by merging delta specs into the main specification set using OpenSpec semantics.
  • Enforces a user-confirmation step and visibility of irreversible actions before archiving.
  • Validates entry state (phase archive, verify_result pass, archived false) and updates archival metadata upon success.

Quick Start

Invoke /comet-archive with the target change name to complete the archival and delta-merge process.

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 delta changes using OpenSpec semantics?

To archive completed delta changes, the process merges delta specs into main specs and moves the change into the archive directory using OpenSpec semantics. This finalization requires a user-confirmation step and discloses irreversible actions before completing.

What is the process for merging delta specs into main specifications?

Merging delta specs into main specifications happens during the archival step, where completed delta changes are finalized using OpenSpec semantics. This mechanism enforces a verified state and updates archival metadata upon a successful merge.

Do I need a verified state before archiving delta specs?

Yes, archiving delta specs requires a verified state. The process validates entry state to ensure phase archive is active, verify_result has passed, and archived is false before allowing the irreversible archival action to proceed.

Why does archiving delta changes require user confirmation?

Archiving delta changes requires user confirmation because the action is irreversible. The mechanism enforces a confirmation step and discloses the finality of the merge to maintain guardrails against reusing archived work.

Can I use spec-management archiving without a comet environment?

No, you cannot use spec-management archiving without a functioning comet environment. The archival process also requires a verified entry in phase archive and the presence of the archive directory to succeed.