archive

Parse change directives and propagate them into documentation specification suites.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill archive-zte-aicloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/archive
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill archive-zte-aicloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive parses change directives from CHANGES_DIR (spec.md, design.md, contracts/*.md) and applies them to DOC_DIR/specs, ensuring that requirements, scenarios, entities, functions, and interfaces stay consistent with implemented changes.

Core Features & Use Cases

  • Parse and interpret change records from spec.md, design.md, and contracts/*.md
  • Update and synchronize DOC_DIR/specs/ requirements, scenarios, logic_entities, functions, and interfaces
  • Refresh scenario/entity/function/interface lists and JSON associations to reflect the latest changes

Quick Start

Run the archive skill to synchronize CHANGES_DIR updates into DOC_DIR specs and update all related metadata.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I keep documentation specs in sync with code changes?

To keep documentation specs in sync with code changes, you parse change directives from your change records and propagate them into the documentation specification suite, ensuring artifacts align with implemented updates.

What is the best way to archive change records into JSON specs and templates?

Archiving change records into JSON specs and templates involves parsing change directives across REQ, SCN, ENTITY, FUNC, and API types, then updating lists and JSON associations to reflect the latest changes.

How do I update requirements and scenarios from spec.md and design.md files?

Updating requirements and scenarios from spec.md and design.md files requires parsing the change directives within them and applying those updates directly to synchronize the documentation specification suite.

Does archiving changes validate cross-references and IDs in documentation specs?

Yes, archiving changes validates IDs, templates, and cross-references within documentation specs, ensuring insertions avoid overwriting existing docs and all associations remain consistent.

Why are my documentation specs not reflecting the latest entity and function changes?

Documentation specs fail to reflect the latest entity and function changes when change records are not properly parsed and propagated into the documentation specification suite to refresh lists and metadata.

Can I update API contracts and interface specs without overwriting existing documentation?

You can update API contracts and interface specs without overwriting existing documentation by validating IDs and cross-references during the archive process to ensure insertions avoid overwriting existing docs.