skills.rest
NSObjects
NSObjectsCOMMUNITY
Explore all skills by this author →
Website𝕏@servenstayGitHub

archiving

Merge delta specs into main specs and archive completed change folders.

4|1|Updated Apr 7, 2026
Search Tags:#workflow#documentation#tasks#archiving#specs#audit-trail#delta-merging
One-click install
npx skills add https://github.com/NSObjects/specpowers --skill archiving
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archiving
Source: https://github.com/NSObjects/specpowers/tree/main/skills/archiving
Command: npx skills add https://github.com/NSObjects/specpowers --skill archiving

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps the spec-driven workflow tidy by ensuring finished work is verified, merged, and removed from active change buckets so nothing lingers unresolved.

Core Features & Use Cases

  • Completion Verification: Review tasks.md to confirm each TDD task is marked complete before proceeding.
  • Delta Spec Merging: Apply ADDED/MODIFIED/REMOVED changes from specs/changes/<name>/specs into the main specs/specs entries, creating new specs when needed.
  • Archival Move & Reporting: Move the change folder into specs/changes/archive with a date prefix while preserving all artifacts and then report the merged spec summary to the user.
  • Use Case: After finishing a feature like a dark-mode spec, run this skill to merge the delta requirements into the core specs and archive the change for auditability.

Quick Start

Archive the current change by confirming all tasks are complete, merging its delta specs into the main specifications, and moving the folder to specs/changes/archive with today's date.

Frequently Asked Questions about archiving

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

FAQPage Schema
How do I archive completed change workflows in spec-driven development?▼

To archive completed change workflows, you verify all tasks in tasks.md are complete, merge delta specs into main specs via ADDED/MODIFIED/REMOVED updates, and move the change folder to specs/changes/archive with a date prefix.

What happens to delta specs when a change workflow is finalized?▼

When finalizing a change workflow, delta specs are merged by applying ADDED, MODIFIED, and REMOVED updates from specs/changes/<name>/specs into the main specs/specs entries, creating new specs when needed.

How do I verify all TDD tasks are complete before archiving specs?▼

You verify TDD task completion by reviewing tasks.md to confirm each task is marked complete before proceeding with the delta spec merging and archival process.

How does archiving preserve artifacts for audit trails in spec-driven workflows?▼

Archiving preserves audit trails by moving the entire change folder into specs/changes/archive with a date prefix, ensuring all artifacts remain intact while removing them from active change buckets.

When should I archive completed specs instead of keeping them in active change buckets?▼

You should archive completed specs once all tasks are checked and delta requirements are merged, ensuring finished work doesn't linger unresolved in active change buckets and maintaining a tidy spec-driven workflow.

Related Skills

Explore More Software Engineering Skills→
LIDR-academyLIDR-academy
273

openspec-sync-specs

Merge delta specs into main specs within the openspec workflow.

Official
Advanced
rozxrozx
25

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict-aware plans and date-based folders.

Community
Advanced
AuroraWebSoftwareAuroraWebSoftware
41

openspec-apply-change

Automate OpenSpec change task implementation and progress tracking via the openspec CLI.

Official
Advanced
a3lema3lem

spexl-archive

Merge spexl change deltas into reference specs and archive them.

Community
Advanced