openspec-archive-change

Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-archive-change-trutoman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-archive-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—artifact completion, task status, and delta spec synchronization—before the change directory can be safely moved to the archive. This Skill automates that verification and archiving process so completed changes are closed out consistently without losing spec updates. ## Core Features & Use Cases - Guided change selection: Infers the change from context, auto-selects when only one active change exists, or prompts with a list of active changes when ambiguous. - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning but not blocking on unfinished items. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Safe archiving: Moves the change directory into a date-prefixed archive folder, failing cleanly if the target already exists. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill confirms all artifacts are done, syncs spec deltas to the main specs, and moves the change into the archive with a summary report. ## Quick Start Archive the completed change "add-user-auth" and sync its delta specs to the main specs before moving it.

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 a completed OpenSpec change?

Invoke the archive workflow with an optional change name; if omitted, the Skill infers it from context or prompts with active changes. It verifies artifacts and tasks, assesses delta spec sync, then moves the change directory into a date-prefixed archive folder.

How does OpenSpec archive handle incomplete tasks or artifacts?

Incomplete artifacts or unchecked tasks trigger a warning showing what remains unfinished, and the user is asked to confirm before proceeding. Archiving is not blocked; the summary notes any warnings such as the count of incomplete tasks.

Does the archive workflow sync delta specs to main specs?

Yes, when delta specs exist the Skill compares them against main specs and prompts to sync before archiving. The sync runs inline and is re-verified; if verification fails, archiving stops so the change directory stays intact.

What happens if the archive target directory already exists?

The archive fails with an error suggesting you rename the existing archive or use a different date. Target names use the change name as-is when already date-prefixed, otherwise the current date is prepended as YYYY-MM-DD.

Can I archive a change stored in a registered OpenSpec store?

Yes, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes. Without a store flag, commands act on the nearest local openspec root.