openspec-archive-change

Archive completed openspec changes and generate retrospective entries.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill openspec-archive-change-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/openspec-archive-change
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill openspec-archive-change-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow, ensuring archival traceability and auditability.

Core Features & Use Cases

  • Archive completed changes by moving the change directory into an organized archive location under openspec/changes/archive/YYYY-MM-DD-<change-name>, preserving metadata like .openspec.yaml.
  • Generate a retrospective entry (retros/<change-id>.md) to capture learnings and actions for future improvements.
  • Validate artifact and task completion via openspec status and prompts to confirm if issues are detected, then complete the archive.

Quick Start

Archive a completed change by moving its directory into the archive under openspec/changes/archive and generate a retrospective entry.

Frequently Asked Questions about openspec-archive-change

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

FAQPage Schema
How do I archive completed openspec changes to preserve change lineage?

Archiving completed openspec changes involves moving the change directory to openspec/changes/archive/YYYY-MM-DD-<name> and generating a retrospective entry. This organizes finished work while preserving metadata like .openspec.yaml for auditability.

What is the best way to write a retrospective for an archived workflow change?

Writing a retrospective for an archived workflow change means creating a retros/<change-id>.md file. This captures learnings and actions for future improvements, ensuring experimental workflow changes are documented after implementation.

How do I verify artifact and task completion before archiving an openspec change?

Verifying artifact and task completion before archiving uses openspec status to check for issues. If problems are detected, the workflow prompts for confirmation to ensure all tasks are truly complete before moving the change.

When should I archive an experimental workflow change instead of leaving it active?

You should archive an experimental workflow change once it has been fully implemented, requires artifact checks, and needs a retrospective write. Archiving organizes finished work and preserves the change lineage for future reference.

Can I move an openspec change to the archive if the status check detects incomplete tasks?

Moving an openspec change with incomplete tasks triggers a confirmation prompt. The archive process validates completion via openspec status first, ensuring you consciously confirm any issues before proceeding with the directory move.

Does archiving an openspec change preserve the original metadata files?

Archiving an openspec change preserves original metadata files like .openspec.yaml. The change directory is moved directly into openspec/changes/archive/YYYY-MM-DD-<name>, maintaining all metadata and ensuring archival traceability.