skills.rest
srnnkls
srnnklsCOMMUNITY
Explore all skills by this author →
GitHub

spec-archive

Archive completed development specs and update their status and index.

1|Updated Jan 12, 2026
Search Tags:#git#workflow#versioning#documentation#archive#specs#project-management
One-click install
npx skills add https://github.com/srnnkls/tropos --skill spec-archive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-archive
Source: https://github.com/srnnkls/tropos/tree/main/skills/spec-archive
Command: npx skills add https://github.com/srnnkls/tropos --skill spec-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed development specs from ./specs/active/ to ./specs/archive/, updating documents with completion status and maintaining archive index. Use when finishing tasks or moving completed work to archive.

Core Features & Use Cases

  • Move specs from active to archive and apply completion statuses in spec.md, tasks.yaml, and context.md.
  • Create or update an archive index at ./specs/archive/README.md and maintain per-spec archives.
  • Optional Git workflow: switch branches, merge checks, and cleanup after archiving.

Quick Start

Run the spec-archive skill to move a completed spec from active to archive and update the archive index.

Frequently Asked Questions about spec-archive

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

FAQPage Schema
How do I archive completed development specs from active to archive directories?▼

Archiving completed development specs involves moving them from active to archive directories while updating completion statuses in spec.md, tasks.yaml, and context.md, and maintaining the archive index.

What is the best way to maintain an archive index for completed project specs?▼

The best way to maintain an archive index is to automatically create or update the README.md file within the archive directory, preserving the structure and historical reference of per-spec archives.

Can I automate git workflow operations when moving completed specs to archive?▼

Yes, you can optionally perform Git workflow operations when archiving specs, which includes switching branches, running merge checks, and executing cleanup after the archival process completes.

When should I move a project specification to the archive folder?▼

You should move a project specification to the archive folder when specs are fully completed, ready for historical reference, or explicitly requested for archival, ensuring status validation beforehand.

Does archiving specs validate the completion status in spec.md before moving?▼

Yes, archiving specs validates the spec.md status before moving files, ensuring that only fully completed or explicitly requested specifications are transferred to the archive directory.

Related Skills

Explore More Software Engineering Skills→
srnnklssrnnkls

spec-update

Analyze git history to align spec documents with actual project state.

Community
Advanced
lepahclepahc
1

kspec-merge

Merge approved Git task branches into integration branches with kspec review gates.

Official
Intermediate
brainsnorkelbrainsnorkel

openspec-bulk-archive-change

Batch-archive multiple completed OpenSpec changes into a date-stamped directory.

Community
Advanced
NightreaverNightreaver
6

ssh_docker_compose_up

Deploy Docker Compose projects across multiple hosts via SSH.

Community
Intermediate