skills.rest
luansilvadb
luansilvadbCOMMUNITY
Explore all skills by this author →
GitHub

specskills-archive-change

Validates artifacts and tasks before atomically archiving completed specskills changes into dated directories.

Updated Apr 16, 2026
Search Tags:#automation#validation#archive#change#delta-specs#specskills
One-click install
npx skills add https://github.com/luansilvadb/agoravai --skill specskills-archive-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specskills-archive-change
Source: https://github.com/luansilvadb/agoravai/tree/main/.rag/context/specskill-archive-change
Command: npx skills add https://github.com/luansilvadb/agoravai --skill specskills-archive-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed change in the specskills workflow by validating artifacts and tasks, evaluating delta-spec synchronization, and moving the directory into a dated archive with explicit user confirmation to prevent silent archiving.

Core Features & Use Cases

  • Validates prereqs: artifacts and tasks are complete or flagged with warnings and prompts the user.
  • Evaluates delta specs against main specs and optionally performs synchronization before archiving.
  • Moves the change directory atomically into specskills/archive/YYYY-MM-DD-<CHANGE_NAME> and preserves the original state.
  • Provides clear warnings and prompts to ensure safe archival, with explicit failure modes and recovery hints.

Quick Start

Run the archive workflow for the finalized change by providing its name when prompted.

Frequently Asked Questions about specskills-archive-change

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

FAQPage Schema
How do I safely archive completed change directories without losing validation state?▼

Archiving completed changes safely requires validating all artifacts and tasks, evaluating delta-spec synchronization against main specs, and moving the change directory atomically into a dated archive only after explicit user confirmation.

What happens to delta specs when archiving a completed change?▼

Delta specs are evaluated against main specs during the archive process and can be optionally synchronized before the change directory is moved into the dated archive, ensuring specification consistency.

Can I automate moving change directories into a dated archive folder?▼

Yes, the workflow automates moving change directories into a specskills/archive/YYYY-MM-DD-<CHANGE_NAME> structure atomically, preserving the original state while enforcing explicit user confirmation to prevent silent archiving.

Why does the archive workflow require explicit user confirmation before moving files?▼

Explicit user confirmation is required to guard against silent archiving, ensuring that incomplete artifacts or unvalidated delta specs are not accidentally moved into the dated archive without user awareness.

How do I handle warnings for incomplete tasks before archiving a change?▼

When incomplete tasks are detected before archiving a change, the workflow flags them with warnings and prompts the user, providing clear failure modes and recovery hints to resolve issues before proceeding.

Related Skills

Explore More Software Engineering Skills→
whatevertogowhatevertogo

openspec-archive-change

Archive completed openspec changes after validating artifacts and delta specs.

Community
Advanced
mazhewittmazhewitt

openspec-archive-change

Archives completed changes from the experimental workflow after implementation.

Community
Advanced
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

Official
Advanced
mishahaninmishahanin
10

linkedin-archive

Move published LinkedIn content into a structured private datastore with git integration.

Community
Advanced