skills.rest
MomoChenisMe
MomoChenisMeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speclink-archive

Archive completed changes in a Spec-Driven Development workflow using the Speclink CLI.

1|Updated Jun 29, 2026
Search Tags:#version control#archiving#change management#spec-driven development#speclink
One-click install
npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speclink-archive
Source: https://github.com/MomoChenisMe/speclink/tree/main/.agents/skills/speclink-archive
Command: npx skills add https://github.com/MomoChenisMe/speclink --skill speclink-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires speclink-cli, and includes scripts (resource) components.

What problem does it solve?

Manages the archival process of completed changes within the Speclink system, ensuring that change histories are preserved while allowing for future updates or deletions.

Core Features & Use Cases

  • Archiving Changes: Securely store completed changes with timestamps and version control.
  • Validation: Ensures that all artifacts and tasks are complete before archiving.
  • User Interaction: Allows for user confirmation on incomplete tasks and artifacts.

Quick Start

Use the 'speclink-archive' command to archive the change named 'add-auth' using the Speclink CLI.

Frequently Asked Questions about speclink-archive

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

FAQPage Schema
How do I archive completed changes in a spec-driven development workflow?▼

To archive completed changes in spec-driven development, you can automate the archival process to validate artifact and task status, ensuring spec database integrity before securely storing the change history with timestamps and version control.

What happens if some artifacts or tasks are incomplete when archiving spec changes?▼

When archiving spec changes with incomplete artifacts or tasks, the system prompts for user confirmation to proceed. This interaction ensures you are aware of incomplete items before the change is securely archived within the version control system.

Do I need the Speclink CLI to automate change archiving?▼

Yes, you need the Speclink CLI installed and operational to use the archival automation. The CLI is a required dependency for executing the validation checks and storing the completed change history within the spec database.

What is the best way to preserve change histories while allowing future updates in spec-driven development?▼

The best way to preserve change histories for future updates is to archive completed changes with timestamps and version control. This secures the historical record while maintaining database integrity for subsequent modifications.

How does validation work before archiving a change in the spec database?▼

Validation before archiving a change checks the completion status of all related artifacts and tasks. This ensures the spec database maintains strict integrity, only archiving changes that meet the defined completion criteria or have explicit user confirmation.

Related Skills

Explore More Software Engineering Skills→
syifansyifan
5

openspec-archive-change

Archive completed changes after verifying artifacts and tasks with openspec CLI.

Community
Intermediate
mor-duongmhmor-duongmh
3

archive

Move completed morkit changes to the archive subfolder and update metadata.

Community
Intermediate
Soju06Soju06
2.6k

openspec-apply-change

Implement OpenSpec change tasks and update progress via the openspec CLI.

Community
Advanced
Key0329Key0329

spectra-archive

Archive completed change records with artifact and task validation via the spectra CLI.

Community
Advanced