sdd-archive

Merge delta specifications into main specs and archive change folders.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-archive-portmeo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Portmeo/rag-chat-project/tree/main/.claude/skills/sdd-archive
Command: npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-archive-portmeo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the final steps of the Software Development الدورة (SDD) cycle by synchronizing specification changes and archiving completed work, ensuring a clean and traceable record.

Core Features & Use Cases

  • Spec Synchronization: Merges delta specifications into the main source of truth, handling additions, modifications, and deletions of requirements.
  • Automated Archiving: Moves completed change folders to a dated archive, maintaining an audit trail.
  • Use Case: After a feature is implemented and verified, this Skill ensures its specifications are integrated into the main documentation and the change is moved to a permanent archive, freeing up active development space.

Quick Start

Archive the change named 'user-authentication-flow' using the openspec artifact store mode.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive completed software development changes and sync specifications?

To archive completed software development changes, you sync delta specifications into main specifications and move the change folder to a dated archive. This handles requirement merging, artifact preservation, and generates verification reporting for completed cycles.

What is spec synchronization in the software development cycle?

Spec synchronization merges delta specifications into the main source of truth, handling additions, modifications, and deletions of requirements. It ensures completed feature specifications are integrated into main documentation during the archive process.

How do I merge delta specifications into main documentation automatically?

You merge delta specifications into main documentation by archiving the completed change. The process automatically synchronizes requirement additions, modifications, and deletions into the source of truth before moving the change folder to a permanent dated archive.

Does the archiving process preserve artifacts and generate verification reports?

Yes, the archiving process preserves artifacts and generates verification reports for completed software development cycles. It moves completed change folders to a dated archive while maintaining a permanent audit trail of the synchronized requirements.

When should I archive completed changes and move folders to a dated archive?

You should archive completed changes and move folders to a dated archive after a feature is implemented and verified. This integrates specifications into main documentation, freeing up active development space while maintaining a traceable record.