skills.rest
mrp4sten
mrp4stenCOMMUNITY
Explore all skills by this author →
GitHub

sdd-archive

Merge delta specs into main specs and archive changes with ISO date paths.

3|Updated Apr 5, 2023
Search Tags:#merge#spec#archive#openspec#delta#change
One-click install
npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-archive-mrp4sten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/mrp4sten/.dotfiles/tree/main/development/IA/opencode/skill/sdd-archive
Command: npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-archive-mrp4sten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed changes by syncing delta specs into the main, source-of-truth specs and moving the change folder to archive, ensuring a clean, auditable SDD lifecycle.

Core Features & Use Cases

  • Delta-to-main sync: Merge delta specifications into the corresponding main spec, updating added, modified, and removed requirements while preserving the rest of the document.
  • Archive workflow: Move the processed change folder into a date-prefixed archive path to maintain an auditable history.
  • Verification-driven process: Triggered after verification reports, ensuring only approved changes are archived and logged for traceability.

Quick Start

Archive a completed change by triggering the orchestrator with the available change data.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I merge delta specs into main openspec specifications?▼

To merge delta specs into main openspec specifications, the orchestrator applies delta merges or full copies into the main specs directory. This updates added, modified, and removed requirements while preserving the rest of the document structure.

What is the best way to archive completed spec changes with an audit trail?▼

Archiving completed spec changes with an audit trail involves moving the processed change folder into a date-prefixed archive path. This ensures a clean, auditable SDD lifecycle with proper traceability for all approved modifications.

Does spec archival require a verification report before processing?▼

Yes, spec archival requires a verification report before processing. The workflow is triggered after verification, ensuring only approved changes are archived and logged for traceability within the SDD lifecycle.

How does delta-to-main sync handle requirements that are not modified?▼

Delta-to-main sync preserves non-delta content by only updating added, modified, and removed requirements. It merges delta specifications into the corresponding main spec while keeping the rest of the document intact.

Can I archive a change folder without providing the change-name to the orchestrator?▼

No, you cannot archive a change folder without providing the change-name. The orchestrator requires the change-name, verification report, and the full change folder contents to apply delta merges and move the change to the archive.

Related Skills

Explore More Software Engineering Skills→
kurojskurojs
2

sdd-archive

Merge delta specifications into main specs and archive completed SDD changes.

Community
Intermediate
gonzalezpazmonicagonzalezpazmonica
47

governance-enterprise

Orchestrate enterprise governance workflows for audit trails, compliance, and certifications.

Community
Advanced
unbound-forceunbound-force
3

openspec-archive-change

Archive completed OpenSpec changes with validation and provenance.

Official
Advanced
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate