openspec-archiving-cn

Merge specification diffs into permanent documentation and create timestamped archives.

9|4|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/forztf/open-skilled-sdd --skill openspec-archiving-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archiving-cn
Source: https://github.com/forztf/open-skilled-sdd/tree/main/skills/openspec-archiving-cn
Command: npx skills add https://github.com/forztf/open-skilled-sdd --skill openspec-archiving-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This archiving workflow consolidates completed change proposals by moving their change directories to a timestamped archive and merging the specification differences into the permanent documentation, ensuring traceability and auditability of deployed changes.

Core Features & Use Cases

  • Timestamped archiving: moves the completed change directory into a time-stamped archive location.
  • Diff consolidation: merges ADDED, MODIFIED, and REMOVED specification differences into the resident specs without breaking links or references.
  • Validation and integrity checks: verifies that all tasks are complete before archiving and validates the resident documentation after merging.

Quick Start

Trigger the archiving workflow for a completed change to move its directory into the archive and merge its specification differences into the resident docs.

Frequently Asked Questions about openspec-archiving-cn

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

FAQPage Schema
How do I archive completed spec changes and merge diffs into permanent documentation?

The archiving workflow handles ADDED, MODIFIED, and REMOVED specification sections by merging these differences into resident documentation. It updates cross-references during consolidation to ensure non-destructive integration of deployed changes into the permanent specs.

What is the best way to ensure documentation integrity when merging specification diffs?

Non-destructive archiving requires a defined workflow that verifies task completion, merges diffs, and creates timestamped archives. Validation hooks check resident documentation post-merge to ensure cross-references remain intact across multi-project environments.

Can I automate consistent archival timing for spec changes across multiple projects?

The archiving workflow supports multi-project environments by enforcing consistent archival timing and integrity checks. It standardizes the process of moving completed change directories to timestamped archives and merging diffs into resident documentation.

Why does my spec diff merge leave broken cross-references in the resident documentation?

Spec diff merges can break cross-references if the workflow lacks validation hooks for resident documentation. A proper archiving workflow updates cross-references during the merge and validates the integrity of resident specs after consolidation.

When do I need to use a timestamped archive for completed change proposals?

A timestamped archive is necessary when consolidating completed change proposals to ensure traceability and auditability. It moves the change directory into a time-stamped archive location, providing a permanent record of the deployed changes.