What is OpenSpec Archiving?

It is a specialized skill for AI coding assistants that automates the transition of temporary feature proposals into permanent, 'resident' documentation once a change is deployed.

How does it handle modified requirements?

It locates the existing requirement in the master documentation, removes the old block, and replaces it entirely with the updated version from the spec-delta file.

Does this skill work with Git?

Yes, the workflow includes best practices for Git commit strategies, suggesting separate commits for merging documentation changes and moving files to the archive.

Can I recover archived specifications?

Yes, because the archive is simply a moved directory within your repository, you can manually restore or reference them from the 'spec/archive/' folder at any time.

When should I trigger the archiving process?

You should use it when a code change is fully implemented, passed all tests, and is ready for or has already been deployed to production.

OpenSpec Archiving & Documentation (CN)

Name: OpenSpec Archiving & Documentation (CN)
Author: forztf

byforztf

•

Learning & Documentation

Archives completed specification changes and merges requirement deltas into permanent documentation for Spec-Driven Development workflows.

About

The OpenSpec Archiving skill is designed for teams practicing Spec-Driven Development (SDD) who need a structured way to transition feature proposals into permanent records. It automates the process of identifying requirement deltas—including added, modified, and removed logic—and accurately merging them into a project's resident specification files. By enforcing a verification workflow and creating timestamped archives, it ensures that your project documentation remains a 'single source of truth' that perfectly reflects the current state of the deployed codebase while maintaining a complete historical audit trail.

Key Features

Markdown structure validation for resident specification documents
Pre-merge verification checklists for implementation and deployment status
Timestamped archival of change directories to maintain immutable history
2 GitHub stars
Automated merging of ADDED, MODIFIED, and REMOVED requirement blocks
Step-by-step workflow tracking to prevent partial or broken documentation updates

Use Cases

Finalizing a feature implementation by merging spec deltas into master documentation
Updating existing project requirements to reflect bug fixes or logic changes in production
Maintaining a searchable archive of all historical architectural changes and proposals

About

Key Features

Markdown structure validation for resident specification documents
Pre-merge verification checklists for implementation and deployment status
Timestamped archival of change directories to maintain immutable history
2 GitHub stars
Automated merging of ADDED, MODIFIED, and REMOVED requirement blocks
Step-by-step workflow tracking to prevent partial or broken documentation updates

Use Cases

Finalizing a feature implementation by merging spec deltas into master documentation
Updating existing project requirements to reflect bug fixes or logic changes in production
Maintaining a searchable archive of all historical architectural changes and proposals