archive

Name: archive
Availability: InStock
Author: MinhQuan

Archive completed OpenSpec changes after verifying code-docs sync and generating changelogs.

Updated Mar 27, 2026

Search Tags:#changelog #archive #openspec #documentation-sync #code-vs-docs #knowledge-export

Ready to run

npx skills add https://github.com/minhquan2904/vibe-check-scam --skill archive-minhquan2904

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/archive
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill archive-minhquan2904

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes after ensuring code-vs-docs synchronization and prepare artifacts for retention, auditing, and knowledge export.

Core Features & Use Cases

Code-vs-Docs Sync: verify that proposal.md, design.md, and specs match the implemented changes.
Changelog & Archival: generate a changelog.md for Change Request variants and move the change into openspec/archive.
Knowledge Export Advisory: flag potential updates to base_knowledge when archiving.
Archive Move: relocate change directory from openspec/changes/<name>/ to openspec/archive/<name>/.

Quick Start

Move the change directory to the archive location after completing the sync check.

Frequently Asked Questions about archive

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

FAQPage Schema

How do I archive OpenSpec changes after verifying code and documentation synchronization?▼

Archiving OpenSpec changes requires verifying that proposal.md, design.md, and specs match your implemented code, then relocating the change directory from openspec/changes/ to openspec/archive/ for retention.

What is a code-vs-docs sync check in an OpenSpec archival workflow?▼

A code-vs-docs sync check verifies that proposal.md, design.md, and specs accurately reflect implemented changes before the change directory is moved into the openspec/archive path for retention.

How do I generate a changelog for a Change Request when archiving completed changes?▼

Generating a changelog during archiving involves determining the CR variant and creating a changelog.md file while moving the completed change into the openspec/archive directory.

When should I flag base_knowledge updates during the change archival process?▼

Flag base_knowledge updates when archiving a change that impacts foundational documentation, triggering an advisory to review potential knowledge export revisions before finalizing the archive relocation.

Can I archive changes without distinguishing between CR and non-CR variants?▼

No, archiving requires determining the CR or non-CR variant because CR variants trigger changelog.md generation, while non-CR variants follow a standard archival path without changelog generation.

What are the limitations of archiving changes without completing doc-sync verification?▼

Archiving without doc-sync verification risks retaining unverified artifacts, as the process enforces that all core artifacts including proposal.md and design.md are included and synchronized before the archive move.