sdd-archive

Archives verified SDD change folders into a dated archive tree with closure reports.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sdd-archive-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-archive
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-v2/skills/sdd-archive
Command: npx skills add https://github.com/nico0695/ai-tools --skill sdd-archive-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a spec-driven development change passes final verification, teams need a consistent, auditable way to close it out. This Skill moves the full active change folder into a canonical archive tree and writes a traceable closure report, preventing lost artifacts and ambiguous project state. ## Core Features & Use Cases - Gated Archival: Only archives changes whose verify verdict is pass or pass_with_warnings, refusing blocked gates, missing verify reports, and the planner objective. - Full-Folder Move with Collision Guards: Relocates the entire active change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/ without overwriting existing archives or dropping artifacts. - Audit-Friendly Closure Report: Generates archive-report.md recording verify verdicts, closeout-review decisions, source and destination paths, and artifact inventory. - Use Case: After sdd-verify returns a passing verdict on a feature change, invoke this Skill to finalize the change, update state.yaml to lifecycle_status archived, and produce a durable closure record. ## Quick Start Archive the verified change folder for my current SDD change and generate its archive report.

Frequently Asked Questions about sdd-archive

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

FAQPage Schema
How do I archive a verified SDD change folder?▼

Run the archive phase after sdd-verify returns a pass or pass_with_warnings verdict. The Skill moves the full active change folder to openspec/changes/archive/YYYY-MM-DD-{change-name}/ and writes an archive-report.md with closure evidence.

What preconditions are required before archiving a change?▼

The verify-report.md must exist with a pass or pass_with_warnings verdict, the archive gate must not be blocked, any required closeout_review must be resolved, and the destination path must not collide with an existing archive.

Can I archive the planner objective in SDD v2?▼

No, the planner objective is explicitly excluded from archival. Planner ends at the planned state, and the archive phase returns blocked if the active objective is planner.

What happens if the archive destination already exists?▼

The archive phase refuses to silently overwrite an existing archive folder. It returns a blocked status when the destination path collides with a different archived change, protecting prior closure records.

Does archiving rerun verification or merge specs?▼

No, archiving trusts sdd-verify as the quality gate and never reruns verification. In the MVP stage it only moves the folder and adds archive-report.md without merging content into project-wide specs.