sdd-archive

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

Updated Nov 19, 2024

Search Tags:#merge #archive #sdd #openspec #specs #audit-trail #engram

Ready to run

npx skills add https://github.com/Strocs/.dotfiles --skill sdd-archive-strocs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-archive
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-archive-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the final step of the SDD lifecycle by synchronizing delta specifications into the main specification set and moving completed change folders into an immutable archive to preserve an audit trail and close out implemented changes.

Core Features & Use Cases

Delta-to-main spec merging: Apply added, modified, and removed requirement changes from a change delta into the authoritative spec while preserving unrelated requirements.
Archive management: Move completed change folders into openspec/changes/archive with ISO-date prefixes and ensure archived artifacts remain intact for auditability.
Mode-aware behavior: Support engram mode to gather artifact observation IDs into an archive-report, openspec mode for direct file merges and moves, and none mode for dry-run summaries.
Safety and validation: Detect destructive merges, enforce verification gates, obey openspec/config.yaml archive rules, and require orchestrator confirmation for risky operations.

Quick Start

Archive the change feature-login by merging its delta specs into the main specs and moving openspec/changes/feature-login into openspec/changes/archive/YYYY-MM-DD-feature-login.

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 specs after implementation?▼

To merge delta specs into main specs, apply added, modified, and removed requirement changes from the change delta into the authoritative spec. This deterministic merge matches requirements by name and preserves unaffected content while moving completed change folders into an audit archive.

What is the best way to archive openspec change folders with ISO-date prefixes?▼

Archiving openspec change folders involves moving completed changes into openspec/changes/archive with ISO-date prefixes. This ensures archived artifacts remain intact for auditability and enforces openspec/config.yaml archive rules during the closure process.

Does the SDD archive process support engram mode artifact gathering?▼

The SDD archive process supports engram mode to gather artifact observation IDs into an archive-report. It also supports openspec mode for direct file merges and moves, plus a none mode for dry-run summaries.

How do destructive merge detection and verification gates work in specification merging?▼

Destructive merge detection and verification gates enforce safety during specification merging by identifying risky operations and requiring orchestrator confirmation. They prevent data loss by validating that changes are verified before archiving implemented deltas.

When should I archive implemented changes in an SDD workflow?▼

You should archive implemented changes in an SDD workflow after verification and before closure. This final step synchronizes delta specifications into the main specification set and moves completed change folders into an immutable archive to preserve an audit trail.

Can I use this SDD archive tool without any external dependencies?▼

You can use this SDD archive tool without external dependencies, as it operates independently to reconcile openspec change deltas or engram-mode artifacts. It performs deterministic merges by matching requirements by name directly within your environment.