spec-archive

Archive spec changes after verification and documentation checks.

9|Updated May 27, 2026
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-archive-kamioj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-archive
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-archive
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-archive-kamioj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the archiving of spec changes, ensuring that they are properly verified and documented before being stored.

Core Features & Use Cases

  • Spec Change Archiving: Automatically archives the current spec change to a secure location with detailed information.
  • Verification: Ensures that the change is verified and that all necessary checks have been completed before archiving.
  • Documentation: Provides a comprehensive audit trail for each change, including divergences, evidence, and deferred items.
  • Use Case: For developers and project managers who need to keep track of all changes made to a spec, ensuring that they are properly documented and reviewed.

Quick Start

Archive the current spec change with the command: $spec-archive

Frequently Asked Questions about spec-archive

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

FAQPage Schema
How do I automate spec change archiving with verification checks?

Spec change archiving is automated by running the archive command, which ensures all verification checks and documentation are completed before securely storing the changes.

What is spec management archiving and when do I need an audit trail for changes?

Spec management archiving stores verified project changes with detailed audit information, needed when tracking divergences, evidence, and deferred items for developer or project manager review.

Do I need a specific directory structure to archive spec changes?

Yes, archiving spec changes requires a specific spec directory structure and specific hooks to be configured for proper operation and automated verification.

How do I verify and document deferred items before archiving a spec change?

Verification and documentation of deferred items happen automatically during the archiving process, which checks that all necessary reviews are completed and records comprehensive audit details.

What's the best way to maintain change tracking for project management specs?

Change tracking for project management specs is maintained by automating the archiving process, which securely stores each change with its verification status, divergences, and evidence.