spec-archiving

Archive completed change proposals and merge specification deltas into living documentation.

Updated Oct 23, 2025
One-click install
npx skills add https://github.com/nextbysam/Saternal --skill spec-archiving
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-archiving
Source: https://github.com/nextbysam/Saternal/tree/main/.claude/skills/spec-archiving
Command: npx skills add https://github.com/nextbysam/Saternal --skill spec-archiving

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed change proposals and merges their spec deltas into the living specification documentation. Archiving signifies deployment and completion.

Core Features & Use Cases

  • Archive operation: move the completed change folder to a timestamped archive.
  • Delta merging: merge ADDED, MODIFIED, and REMOVED deltas into living specs to keep documentation in sync with implementation.
  • Validation & governance: verify completion before archiving and maintain an immutable historical record.

Quick Start

Initiate the archive workflow after deployment to move the change folder, merge delta changes into living specs, and verify completion before finalizing.

Frequently Asked Questions about spec-archiving

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

FAQPage Schema
How do I merge specification deltas into living documentation after a deployment?

To merge specification deltas into living documentation, you archive completed change proposals by moving the change folder to a timestamped archive and integrating ADDED, MODIFIED, and REMOVED deltas into living specs. This keeps documentation synchronized with implementation.

What is living spec governance and how does archiving support it?

Living spec governance maintains synchronized project documentation through verified changes. Archiving supports this by enforcing completion verification before moving change folders to an immutable historical archive, ensuring only validated deltas merge into living specs.

How do I archive completed change proposals in a deployment workflow?

You archive completed change proposals by initiating the archive workflow post-deployment, which moves the change folder to a timestamped archive, merges specification deltas into living docs, and verifies completion before finalizing the immutable record.

Does the archiving process validate living spec structure before merging deltas?

Yes, the archiving process validates the living spec structure before merging deltas. It requires strict verification steps to ensure completion and structural integrity before integrating ADDED, MODIFIED, and REMOVED changes into the documentation.

What is the best way to maintain an immutable historical archive of specification changes?

The best way to maintain an immutable historical archive is to timestamp completed change folders upon deployment and move them directly into the archive, preventing post-merge alterations while keeping living specs updated with merged deltas.

When should I not use automated delta merging for living docs?

You should not use automated delta merging when deployment completion cannot be verified or the living spec structure fails validation, as the workflow requires successful completion checks before archiving change folders and integrating specification deltas.