How does it handle modified requirements during the merge?

It identifies the existing requirement in your living specs and replaces the entire block with the updated content from the delta file to ensure consistency.

Does this skill support git workflows?

Yes, it follows a recommended git commit strategy, suggesting separate commits for merging deltas and performing the archive move for better traceability.

When should I use the OpenSpec Archiving skill?

Use this skill when a proposed change has been fully implemented, tested, and is ready for deployment, or has already been deployed to production.

Can it handle multiple requirements across different files?

Absolutely. The skill is designed to process multiple delta files and update the corresponding living specifications across different capability folders.

What happens to the original change proposal after archiving?

The entire change folder is moved from the active 'changes' directory to a timestamped 'archive' folder, preserving the historical context and keep the active workspace clean.

OpenSpec Archiving

Name: OpenSpec Archiving
Author: forztf

byforztf

•

Learning & Documentation

Archives completed feature changes and merges specification deltas into living documentation for spec-driven development.

About

This skill automates the final phase of the Spec-driven Development (SDD) lifecycle by archiving completed change proposals and synchronizing their specific requirements with the project's living documentation. It systematically handles the addition, modification, and removal of requirements across specification files, ensuring that your project's technical truth remains up-to-date once a feature is deployed. By managing timestamped archives and providing a structured merge workflow, it maintains a clean historical record while preventing the accumulation of stale proposal files in the active development directory.

Key Features

Pre-archive verification checklist to ensure implementation completeness
2 GitHub stars
Automated merging of ADDED, MODIFIED, and REMOVED requirement deltas
Validation of living spec structure post-merge to prevent formatting errors
Creation of timestamped archive directories for historical preservation
Atomic file movement to prevent orphaned documentation files

Use Cases

Finalizing a feature branch by merging new requirements into the main specification
Cleaning up completed change proposal folders after production deployment
Maintaining an immutable history of architectural and requirement changes

About

Key Features

Pre-archive verification checklist to ensure implementation completeness
2 GitHub stars
Automated merging of ADDED, MODIFIED, and REMOVED requirement deltas
Validation of living spec structure post-merge to prevent formatting errors
Creation of timestamped archive directories for historical preservation
Atomic file movement to prevent orphaned documentation files

Use Cases

Finalizing a feature branch by merging new requirements into the main specification
Cleaning up completed change proposal folders after production deployment
Maintaining an immutable history of architectural and requirement changes