sdd-archive

Merge delta specs into main specs and archive change folders.

Updated Jun 22, 2024
One-click install
npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-archive-killoconq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/KilloconQ/dotfiles/tree/main/opencode/.config/opencode/skills/ssd-archive
Command: npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-archive-killoconq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates archiving of completed changes by merging delta specs into the main specs and moving the change folder to an archive, ensuring the source of truth stays up-to-date.

Core Features & Use Cases

  • Delta-to-main merge: merges added, modified, and removed requirements from delta specs into openspec/specs/{domain}/spec.md when the main spec exists.
  • Copy delta as main: when the main spec does not exist, copies the delta as the main spec to openspec/specs/{domain}/spec.md.
  • Archive workflow: moves the entire change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/.
  • Verification & auditing: ensures archive contains proposal, specs, design, tasks, and maintains an audit trail.

Quick Start

Run the sdd-archive skill after verification to merge delta specs into the main specs and move the change folder to the archive.

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 in an OpenSpec workflow?

To merge delta specs into main specs, the skill merges added, modified, and removed requirements from delta specs directly into openspec/specs/{domain}/spec.md, keeping your source of truth up-to-date.

What happens when the main spec does not exist during a delta merge?

When the main spec does not exist during a delta merge, the skill copies the delta spec as the main spec to openspec/specs/{domain}/spec.md to establish the baseline.

How do I archive completed change folders with a date prefix?

To archive completed change folders with a date prefix, the skill moves the entire change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/, maintaining a full audit trail.

What files are required in the archive folder for OpenSpec verification?

The archive folder for OpenSpec verification must contain the proposal, specs, design, and tasks files, ensuring the archive maintains a complete audit trail of the change.

What persistence modes are available for archiving OpenSpec changes?

Available persistence modes for archiving OpenSpec changes include auto, engram, openspec, and none, allowing configurable handling of the merge and archive operations.

When should I run the spec archiving process in my workflow?

You should run the spec archiving process after verification, using the verification report and full change folder to perform the merge and move the changes to the archive.