openspec-archive-change

Archives completed OpenSpec changes after syncing delta specs and verifying merged pull requests.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-archive-change-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-archive-change-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves many error-prone manual steps: checking artifact and task completion, confirming the PR is merged, syncing delta specs into the main specs, moving the change directory into the archive, committing the result, and updating Jira. This Skill automates that entire close-out sequence so nothing is forgotten. ## Core Features & Use Cases - Validated archiving: Runs openspec status and openspec archive --skip-specs to verify artifact completion and move the change into openspec/changes/archive/YYYY-MM-DD-<name>/. - Mandatory spec sync: Automatically applies delta specs to the main specs via the openspec-sync-specs skill before archiving, aborting if the sync fails. - Delivery and cleanup checks: Confirms the change's PR is merged with gh pr list, commits the archive and spec changes, offers Git worktree cleanup, and transitions the linked Jira ticket to "Finalizado". - Use Case: After merging the PR for a change like add-supplier-orders, ask the agent to archive it; the Skill verifies tasks are complete, syncs specs, archives the change, commits, and closes the Jira ticket. ## Quick Start Archive the completed OpenSpec change named add-supplier-orders and sync its delta specs into the main specs.

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?▼

Run the archive workflow with a change name, or let it prompt you with the list of active changes from `openspec list --json`. It checks artifact and task completion, syncs delta specs, then runs `openspec archive <name> --skip-specs -y` to move the change into the dated archive directory.

What happens if tasks or artifacts are incomplete when archiving?▼

The Skill counts incomplete tasks marked `- [ ]` and checks artifact status via `openspec status --json`. If anything is incomplete, it shows a warning and asks for confirmation before proceeding, so archiving is never silently blocked.

Does archiving require the pull request to be merged first?▼

Yes, archiving is treated as post-delivery cleanup. The Skill runs `gh pr list --state merged --search <change-name>` and warns if no merged PR is found, asking for confirmation before continuing.

Can I archive a change without syncing delta specs?▼

No. When delta specs exist, syncing them into `openspec/specs/` is mandatory and happens automatically before the archive move. If the sync fails, the archive aborts so specs never drift from the archived change.

Why does the archive fail with an existing directory error?▼

The CLI fails if an archive for the same date and name already exists. Rename the existing archive or run the archive on a different date; a manual `mkdir`/`mv` fallback is only used when the openspec CLI is unavailable.