sdd-archive

Merge completed delta specifications and preserve audit trails for archived SDD changes.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-archive-zmynxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-archive
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-archive-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incomplete or inconsistent software change records by synchronizing completed SDD artifacts and preserving an auditable archive of the development cycle.

Core Features & Use Cases

  • Spec Synchronization: Merge completed delta specifications into source-of-truth specs while preserving existing requirements.
  • Archive Validation: Check task completion, verification status, and artifact consistency before closing a change.
  • Use Case: When a software feature implementation has passed verification, use this Skill to finalize the SDD lifecycle by updating specifications and moving the completed change into an archive.

Quick Start

Use the sdd-archive skill to archive the completed change after implementation and verification are complete.

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 changes after specification verification?

To archive completed software changes, you synchronize completed delta specifications into source-of-truth specs and move the finalized artifacts into an archive. This preserves an auditable trail of the development cycle.

What does specification synchronization do when finalizing a software change?

Specification synchronization merges completed delta specifications into source-of-truth specs while preserving existing requirements. This ensures your source-of-truth documents accurately reflect the verified implementation before archiving.

Can I archive an SDD change if the task verification is incomplete?

You cannot archive an SDD change with incomplete verification. The archive process requires validating task completion status, verification review results, and artifact consistency before moving the change to the archive.

When do I need to archive SDD changes in a development lifecycle?

You need to archive SDD changes after a software feature implementation has passed verification review. Use this step to finalize the lifecycle by updating specifications and moving the completed change into an archive.

What is the best way to preserve an audit trail for completed development cycles?

The best way to preserve an audit trail is by validating task status and persisting archive reports during the archival process. This synchronizes artifacts and ensures change lifecycle management compliance.