archive

Merge delta specifications into the baseline and archive completed changes.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/augentic/specify --skill archive-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/augentic/specify/tree/main/plugins/spec/skills/archive
Command: npx skills add https://github.com/augentic/specify --skill archive-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of finalizing software changes by merging updated specifications into the baseline and archiving completed work, ensuring a clean and organized project history.

Core Features & Use Cases

  • Spec Merging: Integrates delta specifications into the main baseline, handling additions, modifications, and deletions.
  • Lifecycle Management: Moves completed changes to an archive, maintaining a clear distinction between active and finished work.
  • Validation: Performs coherence checks on merged specs to ensure consistency and adherence to defined formats.
  • Use Case: After implementing a new feature, use this Skill to merge its detailed specifications into the project's master spec file and then archive the feature's development artifacts.

Quick Start

Archive the current change by confirming the merge of its specifications into the baseline.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I merge delta specifications into a baseline after completing a software change?

Merging delta specifications into a baseline involves validating task completion, previewing merge operations, and executing spec merges via a Python script. The workflow then performs baseline coherence checks to ensure consistency before archiving the completed work.

What is the best way to archive completed software development changes and update project metadata?

The best way to archive completed changes is by merging updated specifications into the master spec file and moving development artifacts to an archive. This lifecycle management maintains a clear distinction between active and finished work while updating metadata.

Does this archiving workflow require Python 3 to execute spec merges?

Yes, this archiving workflow requires Python 3 to execute spec merges. The skill relies on Python scripts to integrate delta specifications into the main baseline and perform the necessary coherence checks during the finalization process.

How do I validate artifact and task completion before archiving a git workflow change?

Validating artifact and task completion before archiving is handled automatically by the workflow. It checks that development tasks are complete, previews the merge operations, and ensures baseline coherence before moving the changes to the archive.

When should I use a specification merging workflow for version control archiving?

Use a specification merging workflow for version control archiving when you need to finalize a software development change. It is ideal for integrating additions, modifications, and deletions into the master spec file and moving finished work to a clean archive.