superspec:archive

Apply delta changes to main specs and archive documents after verification.

3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superspec:archive
Source: https://github.com/HankLiu447/SuperSpec/tree/main/skills/archive
Command: npx skills add https://github.com/HankLiu447/SuperSpec --skill superspec-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes after verification passes to preserve complete history and ensure traceability between delta specs and main specs.

Core Features & Use Cases

  • Automatically apply delta changes to the main specs.
  • Move associated documents to a date-stamped archive for traceability.
  • Validate the final state after archiving to ensure consistency.

Quick Start

Use the archive skill after a successful verification to archive changes and update the main specs accordingly.

Frequently Asked Questions about superspec:archive

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

FAQPage Schema
How do I archive delta specs to preserve version control history?

To archive delta specs, apply the verified delta changes to your main specs and move associated documents to a date-stamped archive directory. This ensures full traceability between delta specs and the updated main specs.

What is delta diff spec management for completed changes?

Delta diff spec management is the process of applying incremental specification changes to main specs after verification. It automates updating main documents and moving delta records to a timestamped archive for historical consistency.

When should I archive delta changes in spec management?

You should archive delta changes immediately after a successful verification pass. Archiving validates the final state and ensures traceability between the applied delta diffs and the main specs.

How do I apply delta changes to main specs in the correct order?

You apply delta changes to main specs by using repository tooling to execute the defined application order. The archive skill automates this process and produces a structured archive under the changes directory.

Does spec archiving require any specific repository tooling?

Yes, archiving specs requires repository tooling to run verification, apply deltas in the defined order, and produce the structured archive. There are no external dependencies, but the repository environment must support these operations.

What is the best way to trace archived spec changes back to main specs?

The best way to trace archived spec changes is to use a date-stamped archive directory. This validates the final state after applying delta changes and preserves the complete history linking delta specs to main specs.